Identifying and Parameterizing Roof Types in Map Data

ABSTRACT

Methods and apparatus for a roof analysis tool for constructing a parameter set, where the parameter set is derived from mapping data for a map region, and where the parameter set describes the roofs for the buildings within the map region. In some cases, the parameter set includes a list of roof type identification values and the respective buildings in the map region for which a given roof type identification value corresponds. The roof analysis tool may operate on a server and work in conjunction with a mobile device, where the mobile device may display map views of a map region such that the map view is based on a three-dimensional model of the map region, and where a portion of the three-dimensional model is based on data generated on the mobile device and a portion of the three-dimensional model is based on data generated on the server.

This application claims benefit of priority to U.S. Provisional Application Ser. No. 61/655,910, entitled “Identifying and Parameterizing Roof Types in Map Data,” filed Jun. 5, 2012.

BACKGROUND

Mobile devices often provide various mapping related features such as displaying a map view for a region in various modes and according to various viewpoints. Traditional mapping applications operable on mobile devices receive raster image data for a given map region of a map view. However, raster data is unusable for creating three-dimensional models of a map region and a corresponding three-dimensional map view of the map region. Further, within a map view of a map application executing on a mobile or desktop device, a user may prefer to see a representation of the surrounding environment in an aesthetically simple rendering. For example, as a user walks down a street while referencing the map view provided by a mobile device, a user may find it easier to navigate if surrounding structures in the map view were stripped of unnecessary and distracting details, texture or other information that may not be related to navigation or identification of the structure. In some cases, the map view may be three-dimensional, and in such a case a map view that is a simplified version of the real world may allow a user to make quicker navigation decisions.

SUMMARY

In one embodiment, a mobile device may use map data for a map region to be displayed in a map view. From the map data the mobile device may construct a three-dimensional model to serve as the basis for rendering a three-dimensional map view of the map region. Further, the mobile device may construct a portion of the three-dimensional model and construct another portion of the three-dimensional model based on data provided from a server. The data from the server may be a parameter set describing each of the planes of a roof on each building in the map region, or the parameter set may simply identify roof types for each building and the mobile device may use the roof types as the basis for rendering roofs for the buildings in the map view. Further, in some cases, the parameter set may include information such as texture information corresponding to a given roof, where the texture information may be extracted from three-dimensional mesh data.

For example, a mobile device may construct a three-dimensional model of a map region where the buildings in the three-dimensional models are based on footprint data from a two-dimensional data set corresponding to the map region such that the footprint is extruded to a height value based on a three-dimensional data set also corresponding to the map region. While the constructed three-dimensional model on the mobile device represents an approximation of a building, the extrusion of the footprint to a given height may not provide an accurate representation of the roof of the building.

However, the computational complexity, bandwidth, or storage demands related to processing the map data on the mobile device to construct roof representations for the buildings in a map region based on high definition mapping data may prevent the mobile device from providing a user with a responsive experience using the mapping application. Therefore, in some cases, to generate a more accurate three-dimensional model of a map region, a server may perform calculations, in response to a request or prior to a request, in order to produce a set of parameters describing the different roofs for the different buildings in the map region. Once parameterized, the roof descriptions corresponding to the parameters of the roof may be stored or cached on the mobile device. When the mobile device is provided the set of parameters produced on the server, the mobile device may combine the three-dimensional model constructed on the mobile device with the set of parameters received from the server in order to produce a three-dimensional model of the map region that includes representations of roofs.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is an illustration of a mobile device, according to some embodiments.

FIG. 1B is a diagram illustrating example components within a mobile device, according to some embodiments.

FIG. 2 illustrates a touch screen on a mobile device, according to some embodiments.

FIG. 3A illustrates another mobile device configurable to operate in conjunction with a roof analysis tool, according to some embodiments.

FIG. 3B depicts elements of a map service operating environment, according to some embodiments.

FIGS. 4A-4E depict example flowcharts corresponding to different embodiments of a roof analysis tool, according to some embodiments.

FIGS. 5A and 5B depict illustrations of various map views, according to some embodiments.

FIGS. 6A-6G illustrates various representations of data used by a roof analysis tool, according to some embodiments.

FIG. 7 illustrates a non-exhaustive list of example roof types, according to some embodiments.

FIG. 8A illustrates a roof analysis module, according to some embodiments.

FIG. 8B illustrates a map tool module, according to some embodiments.

FIG. 9 depicts elements of an example computer system capable of implementing a roof analysis tool.

While the invention is described herein by way of example for several embodiments and illustrative drawings, those skilled in the art will recognize that the invention is not limited to the embodiments or drawings described. It should be understood that the drawings and detailed description are not intended to limit the invention to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention. The headings used are for organizational purposes only and are not meant to be used to limit the scope of the description. As used throughout this application, the word “may” is used in a permissive sense (meaning “having the potential to”), rather than the mandatory sense (meaning “must”). Similarly, the words “include”, “including”, and “includes” mean “including, but not limited to.”

DETAILED DESCRIPTION OF EMBODIMENTS

Various embodiments are presented of a roof analysis tool for constructing a parameter set, where the parameter set is derived from mapping data for a map region, and where the parameter set describes the roofs for the buildings within the map region. In some cases, the parameter set simply includes a list of roof type identification values and the buildings in the map region for which a given roof type identification value corresponds. The mapping data may include coordinates for a footprint of a building for which a roof type may be determined, and the mapping data may also include coordinates for points in three-dimensional Cartesian space corresponding to the roof of the building. In some cases, the mapping data may be three-dimensional digital surface model (DSM) meshes and the metadata tagged geographic information system (GIS) footprint data.

In some cases, a mobile device may operate in conjunction with a roof analysis tool operating on a server to produce a map view for a map region, where the map view is based on a three-dimensional model of the map region, and where the mobile device and the server each provide a representation of a portion of the three-dimensional model. However, while the mobile device may operate in conjunction with the roof analysis tool on the server, the roof analysis tool may, prior to any communication with a mobile device, calculate and store parameter sets corresponding to building footprints for any portions of any map region of the world or all map regions of the world. The calculations by the roof analysis tool may be performed once and stored and then updated when new map information is received. When a mobile device or other device requests information for describing a roof or roof type for a given map region or footprint coordinate, the pre-calculated and stored parameters sets are indexed and a parameter set corresponding to the map region or footprint coordinates may be returned.

For example, a mobile device may receive mapping data for a map region to be displayed in a map view of a mapping application. In some cases, the mapping data may be vector-based data from which the mobile device may generate a portion of a three-dimensional model of the map region, and where the three-dimensional model serves as the basis for rendering a three-dimensional map view of the map region. In constructing the three-dimensional model the mobile device may use footprint data from a two-dimensional data set corresponding to the map region such that the footprint is extruded to a height value based on a three-dimensional data set also corresponding to the map region. While the constructed three-dimensional model on the mobile device represents a rough approximation of a building, the extrusion of the footprint to a given height may not provide a representation of the roof of the building that corresponds to the physical dimensions of the roof in the map region.

Further in this example, the computational complexity, bandwidth demands, or storage requirements on the mobile device to construct roof representations for the buildings in a map region based on the mapping data may prevent the mobile device from providing a user with a responsive experience using the mapping application. Therefore, in some cases, to generate a more accurate three-dimensional model of a map region while providing a responsive user experience, a server may perform calculations on the two-dimensional and three-dimensional data sets in order to produce a set of parameters describing the different roofs for the different buildings in the map region. When the mobile device is provided with the set of parameters produced on the server, the mobile device may combine the three-dimensional model constructed on the mobile device with the set of parameters received from the server in order to produce a three-dimensional model of the map region that includes representations of roofs based on the mapping data.

In this way, a three-dimensional map view of a map region may be displayed to a user within the mapping application such that the three-dimensional map view depicts roof shapes for buildings where the roof shapes are representative of the roof shapes of the actual buildings described by the mapping data for the map region. In general, the roof shapes are described as clean, or low-parameter versions of the actual roof, and the low-parameter version of the roof may be used instead of or together with actual roof data. While in this example, the roof shapes depicted in the map view are representative of the actual roof shapes in a map region, in some cases, the roof analysis tool may generate parameter sets of roof shapes that are not based on the mapping data for a map region. In this way, even though the roof shapes in the parameter set bear no correspondence to the actual roof shapes, the map view based on a three-dimensional model incorporating the roof shapes described by the parameter set provide the map view with an additional level of realism if not accuracy.

In some embodiments, instead of a server sending a set of parameters with parameter values describing a roof of a building, the server may send an indication of the type of roof of the building and not additional information describing the shape of the roof. For example, given a number of different archetypal roof styles, the roof analysis tool may determine which of the different archetypal roof styles the mapping data for a building footprint matches. In this way, while the archetypal roof style provided to a mobile device may not be exactly representative of the actual building roof, the roof style used by the mobile device to construct a map view including the building with the roof style may be a close approximation of the actual building. In this example, in order to render a roof type for a building in a map view, the mobile device would receive information regarding the different roof types and identifiers for each of the different roof types, where the different roof types and identifiers are also stored on the server implementing the roof analysis tool. Further, when the mobile device later renders a map view of a map region and the mobile device receives, for a building in the map region, an identifier corresponding to the building, the mobile device may scale, possibly disproportionately, the archetypal roof type corresponding to the received identifier to conform to the footprint of the building.

In some embodiments, a server may begin determining a roof style for a building based on two sets of data, one set of data including building footprint data for a map region and another set of data including three-dimensional mesh data for the map region. An example footprint, footprint 610, for a building in a map region may be seen in FIG. 6B, and where the footprint 610 corresponds to the building with roof plane 602 in FIG. 6A. The mesh data may include vertices and triangles for points in 3D space, and where the triangles in the mesh data may depict a surface of the triangle. An example rendering of the mesh data into a three-dimensional digital surface model may be seen in FIG. 6A, where a roof plane, plane 602, corresponds to one of the planes of a roof of a building. An example of the mesh data, depicted as triangles such as triangle 620 and triangle 622, may be seen in FIG. 6C. In this example, the map region is determined based on coordinate data provided by a mobile device. Once the server determines a roof type for a given building in the map region, the server may provide the mobile device with information on which to base a rendering of the roof type for the given building within a map view of the map region.

In this example, for the server to provide a mobile device with a compact representation of a roof type, the server may determine a representation for a set of planes, including the coordinates of each respective plane, a normal for each respective plane, the size of each respective plane, or the dimensions of each respective plane. In some embodiments, instead of using normals, the roof analysis tool may determine the shape of a roof based on a tangent plane, in other words, using each triangle in the roof. The compact representation, or compact parameters are compact because the roof type representation does not include raster data, but rather the roof type is represented with data which serves as the basis for the mobile device to interpret and render a roof based on the data. In some cases, the compact representation may be a parameter set including an archetypal roof type classification along with an identification for a building within a map region for which the archetypal roof classification corresponds. In other cases, the compact representation may be a parameter set including coordinate data for a plane or planes in a roof along with an identification for a building within a map region for which the roof plane coordinate data corresponds. The coordinate data for a given roof plane may indicate points in three-dimensional Cartesian space that correspond to the points on the corners of the given plane. In other cases, the coordinate data may be represented as spherical coordinates, or latitude/longitude/altitude coordinates, among other options.

In this example, to identify a single plane corresponding to a roof of a building, the roof analysis tool uses the footprint data for a building in the map region to identify mesh data that corresponds to the region in the map area for the building footprint. For example, given the area and coordinates for a footprint, the roof analysis tool may determine the corresponding area and coordinates for the footprint within the mesh data in order to extract the three-dimensional data that corresponds to the footprint. Given the mesh data for the footprint, the roof analysis tool may identify multiple points at one or more heights that correspond to a roof for the building footprint.

Further, in some embodiments, the roof analysis tool may receive two-dimensional footprint data and three-dimensional coordinates for different points on a roof corresponding to a footprint specified within the footprint data. Given the three-dimensional coordinates for the points on the roof, the roof analysis tool may calculate a normal from a plane defined by a set of three or more adjacent or proximate points on the roof. In this way, given multiple respective planes defined by multiple, different respective sets of points, the roof analysis tool may calculate a normal for each plane. Given the calculation of normals for the roof, the roof analysis tool may proceed to remaining calculations for identifying a roof type. In other embodiments, the roof analysis tool may use vertex normal, which may be calculated as the weighted average of all the surface normal of the triangles that surround a given vertex, where the given vertex is common to the adjacent triangles. In this example, the weighting is proportional to the surface area of the triangles.

In some embodiments, in order to identify the data with which the roof analysis tool may determine a roof type for a building in a map region, the input data sets are co-registered to the same coordinate system. As noted above, one input data set may be two-dimensional footprint data (as in FIG. 6B) and another data set may be three-dimensional digital surface model data (as in FIG. 6A), where each data set may be represented in a different coordinate system. Therefore, the roof analysis tool may first convert each data set to a common coordinate system. However, in some cases, even when each data set is represented in the same coordinate system, an element in one data set at a given coordinate may not be in the other data set at the same coordinate. In other words, while the data sets represent approximately the same map region, there may be misalignments between the data sets. To align the data sets, a region from one data set may be warped or molded to fit to the other data set. For example, for a map region of a metropolitan area, common landmarks may be matched in the two data sets, and given the aligned common landmarks, the remaining elements in the data set being warped are warped to match the other data set. One method for accomplishing the alignment of the data sets is through the use of a least squares algorithm, among other possible algorithms. Once the footprint data set and the 3D mesh data set are aligned, the roof analysis tool may iterate over each building in the footprint data and use the coordinate data for each building to extract the 3D mesh data corresponding to the building. Given that 3D mesh data is high definition and includes many data points and triangles, among other information such as texture information, in one embodiment, the mesh data is stored in, for example, a k-d tree and indexed using spatial coordinates. In this way, as the roof analysis tool is iterating through the buildings, the roof analysis tool may use the coordinates of the current building to index in to the k-d tree to extract the corresponding 3D mesh data. Given 3D mesh data for a given footprint, the roof analysis tool may proceed to identify a roof type for the building.

As noted above, the multiple points on a roof of a building may be organized as triangles, where a given triangle has a surface. The roof analysis tool may use the surface of the triangle as the basis of calculating a normal to the surface of the triangle. To calculate the normal to the triangle, the roof analysis tool may use the cross product of any two sides of the triangle. The roof analysis tool may repeat the calculation of a normal for each of the triangles corresponding to the mesh data corresponding to the footprint of a building. An example depiction of the calculated normals may be seen in FIG. 6D, which includes example normal vectors 630, 632, 634, 636, 638, and 640. In this example, each of the normals, or normal vectors, is calculated to be perpendicular to the surface of a roof plane. Further, in some cases, normals may be calculated at sampled points on a regular grid—without a mesh.

In this embodiment, the parameterization of a given normal represented by (nx, ny, nz) may be seen in FIG. 6E, where point 648 a is the point on the roof surface for which the normal is calculated and point 648 b is the tip of the normal, and where axis 644 is the x-axis, axis 642 is the y-axis, and axis 646 is the z-axis. Further in this embodiment, given that the direction of the normal is what is used to determine a grouping of normals, we reduce the vector normal parameterization from three spatial coordinates to two spherical coordinates. In this example, the spherical coordinatization is by angle ρ (rho) 649 a and angle ψ (psi) 649 b. Further, in a spherical coordinate representation of a normal, the angle ρ (rho) 649 a is the angle between the z-axis and a projection of the normal onto the x-z plane, and where the projection of the normal onto the x-z plane corresponds to line 647 a, and where the ψ (psi) angle 649 b is the angle between the normal vector and the y-axis, where the normal corresponds to vector 647 b.

Further, any two-dimensional parameterization may be used, and another coordinate option for representing the normals would be θ-φ (theta-phi). In cases when a Hough transformation is used, the two-dimensional parameterization feeds into the analysis and Hough transform. However, using θ-φ (theta-phi) coordinates would result in normals for flat roof surfaces being close to the z-axis, and hence, due to possible noise in the data, the normals would have azimuth angles that span the entire 0-360 degree range. A consequence would be greater difficulty in finding clusters in the Hough domain for flat roofs, where a Hough transformation to create a Hough domain is one method for finding groups or clusters of normals. By contrast, using the ρ-ψ (rho-psi) parameterization of a normal results in the y-axis becoming the axis presenting difficulties in finding clusters in a Hough domain, but since vertical roof surfaces are relatively unimportant, the ρ-ψ (rho-psi) parameterization is used in this example. In some embodiments, another parameterization option is to use the x, y values themselves which may provide better resolution for steep angles, or roof planes angles that point sharply upward.

As noted above, given the calculation of normals for multiple points on a roof, a Hough transformation may be performed on the normals to generate a two-dimensional (2D) histogram, which can be interpreted as a probabilistic heat map, for example, as depicted in FIG. 6G, In this example, clusters in the 2D histogram 698, or heat map, are selected using a given mass threshold, for example 0.93 (or 93%) of a maximum value. Further, the threshold may either be a fixed absolute value, a relative value such as a percentage of the maximum value, or the threshold may be determined locally based on the data. In this way, the average vector of each cluster may be output as the planar surface normal for the entire cluster. Further in regard to FIG. 6G, histogram 698 depicts a Hough transform of all roof triangle surface normals that are less than 80 degrees off of the z axis. For example, the roof analysis tool may iterate over all normals and calculate two angles for each normal, the rho and psi angles, and place a point in the histogram at the point corresponding to the calculated rho and psi angles for each normal. In histogram 698, the four clusters are clusters 682, 684, 686, and 688. As another example of a histogram generated through a Hough transformation, histogram 699 is a Hough transform of roof triangle surface normals with a bin count greater than 4, and the four clusters are clusters 690, 692, 694, and 696. Using a Hough transform, most normals on a given plane or surface would fall in to the same bin. Further, for a given cluster, the centroid of a given cluster may be taken as the average normal for the cluster and provide a nominal orientation for a roof plane. Given identified clusters, the roof analysis tool may iterate over each normal and classify each normal according to which average normal for a cluster the normal is nearest. As noted earlier, FIG. 6D depicts several clusters of normals for a roof, and the clusters may be used to detect if a roof is flat or not within a given probability.

Further, based on the calculated clusters the roof analysis tool may determine a respective plane corresponding to a respective cluster of normals, where the average vector of the cluster may be defined to be the planar surface normal for the respective plane. FIG. 6F includes various planes that correspond to the various clusters of normals in FIG. 6D. For example, plane 650 corresponds to cluster of normals 630, and plane 652 corresponds to cluster of normals 638. This identification of planes may be repeated for each of the clusters of normals within FIG. 6D.

However, it may be the case that identified planes corresponding to the groups of normals may be separate in space. Therefore, to determine a parameter set for planes that align and meet as the planes of a roof would align and meet, the roof analysis tool may perform additional steps such as mesh filtering and a convex hull analysis of classified roof plane triangles corresponding to the mesh filtering results. For example, given the determined clusters of normals, the roof analysis tool may classify each of the triangles in the three-dimensional mesh data corresponding to the points on the roof, such as the classification of triangle 621 and classification of triangles 623 in FIG. 6C. However, holes, such as hole 624, may be present as a result of chimneys, roof vents, rooftop mounted machinery, or possibly any item or object that is not flat to the roof. These holes are areas within the bounded mesh roof data that are small enough and possibly irregular enough to not result in a cluster of vector normals that exceed a threshold, according to, for example, a Hough transformation. To eliminate the holes, the roof analysis tool may grow the mesh area around the hole and classify the area of the hole according to the classification of the majority of triangles surrounding the hole. For example, hole 624 is surrounded by triangles classified according to a single cluster, and therefore hole 624 is classified to be part of the same classified triangles. Once each hole has been covered, the classified mesh triangles may be converted to a corresponding plane, such as in FIG. 6F, whose planes correspond with the classified mesh triangles in FIG. 6C. From the planes in FIG. 6F, the roof analysis tool may then determine a set of adjoining planes that do not overlap and that may be described with a parameter set that includes coordinate values for each of the component planes in the roof.

In some embodiments, regardless of the actual roof type, a roof analysis tool may interpret a roof to be either flat (or horizontal) and non-flat roofs. For example, if all or most of the normals have a rho angle close to zero and a psi angle close to 90 degrees, then the normal is pointing relatively upward, indicating a flat roof. In this example, the roof analysis tool may use a threshold value in order to determine whether or not the roof is flat, for example, if greater than half of the normals have rho angles close to zero and psi angles close to 90 degrees, then the roof analysis tool may determine the roof is flat, and non-flat otherwise. Other thresholds may also be used, where the threshold is defined prior to the determination of whether the normals have rho angles close to zero and psi angles close to 90 degrees.

However, in embodiments where the roof analysis tool determines an actual roof type, once each plane in a roof of a building has been identified, each of the planes may be parameterized, or otherwise represented in a compact format. In some cases, the planes determined to correspond to groups of normals may overlap, as reflected in FIG. 6F. Further, the outline or perimeter of a given plane may not be composed of straight lines, as reflected by plane 652 in FIG. 6F. Therefore, to generate a parameterized version of the planes, the roof analysis tool may fit each given plane to a polygon and also fit each of the polygons together to form a set of planes that do not overlap and that are made of straight lines. In other cases, the roof analysis tool may simply eliminate the overlap for the different planes and create a parameter set each of the resulting planes. Once a parameterized set of data has been defined, the roof analysis tool may store the parameter set or provide the parameter set for the roof of the building to a mobile device or desktop computer requesting roof information in order to render a map view of a map region.

Further, given a database of possible roof types, these clusters may be used to match a roof type for a given building. For example, given a (non-exhaustive) list of roof types in FIG. 7, the roof analysis tool may determine that the clusters of normals for the roof in FIG. 6D may match roof type 702, which is a hip and valley type roof. As for identifying a roof type based on clusters of normal, several method may be used, for example, a probabilistic machine learning based classifiers (such as a support vector machine), a neural network, or a classification tree (or forest of boosted trees). For the machine learning identification methods, an example training set may be multiple pairs of respective example normal clusters and a respective corresponding roof type. In this way, where a mobile device stores a corresponding database of roof types, the roof analysis tool may transmit a roof type indicator without transmitting the parameters defining the actual roof planes of a roof of a building determined through the process used to determine the roof type. For example, in cases when the mobile device constructs a three-dimensional model that includes an extrusion of a footprint for a given building, the roof analysis tool may simply transmit roof type “A”, or any other identification value, and the mobile device may then interpret the roof type and render the indicated roof type on top of the corresponding building. In cases when the mobile device does not construct a representation of the building extruded to a height value, the roof analysis tool may transmit coordinates for the footprint, a height value, and an identification value for the roof type corresponding to the footprint. In some cases, the mobile device, in requesting roof type parameters, may specify elements to be included in the parameter set, such as footprint coordinates, a parameterized set of planes making up the roof, a roof type identification, or a height value corresponding to the footprint, where the height value may be calculated from a average of height values from vertices in the roof triangles, or the height value may be based on a single random sample of a roof triangle vertex. Further, for the given roof type, the roof analysis tool may simply scale the dimensions of the roof type to match the dimensions of the footprint of the building and render the roof at the top of a three-dimensional version of the building. While in this example, the planes of the roof rendered for the building may not match the real world planes of the roof of the building, the roof type may be similar, thereby still providing a semblance of the real world.

In one embodiment, as an alternative to using a Hough transform (or other transform) based approach, the roof analysis tool may determine between whether or not the roof is a flat roof, and if the roof is flat then the roof analysis tool provides a parameterization indicating a flat roof. If the roof is not flat, the roof analysis tool may select a default non-flat roof type, or the roof analysis tool may randomly select from a list of non-flat roof types and provide a parameter set indicating the selection. For example, the roof analysis tool may, for the points on the roof extracted from three-dimensional mesh data, calculate the variance of the z values for the three-dimensional Cartesian coordinates of each point. The roof analysis tool may then sort the variances, and if there is a low variance, the roof analysis tool determines the roof to be flat, and non-flat otherwise. The roof analysis tool may base the determination on whether the variance is low enough through the use of a threshold value that is defined prior to analyzing the points on the roof, where if the variance is above the threshold then the roof is determined to be non-flat.

In some embodiments, the roof analysis for buildings may be done before any data regarding roof types is requested. For example, for every map region, or in some cases for the most popular map regions, the roof analysis may be performed in parallel on one or more servers or server farms. In such a parallel approach, a given server may be tasked to work on a given map region.

In some embodiments, a mobile device may entirely perform the calculations described herein to determine a roof shape for a building within a map region, where the calculations are based on the mapping data for the map region.

In some embodiments, the server may perform the calculations described herein to determine a roof shape for a building within a map region, where the calculations are based on the mapping data for the map region. In some cases, the server may receive high-resolution three-dimensional mesh data depicting the surfaces within a map region as represented according to multiple triangles.

In some embodiments, given the 3D mesh data for a map region, the roof analysis tool may reference a two-dimensional data set that includes footprint data, where the two-dimensional data set corresponds to the map region. The footprint information may include the location and dimensions of the physical boundaries of a given building within the map area. For example, in a simple case of a square building, the footprint may specify the locations of each corner of the building along with the length of each side of the building. In this example, if the square building has two stories and a flat roof, a simple cube may provide an accurate representation of the volume and dimensions occupied by the building within the map region. Further, as described above, a depiction of a simple cube may provide a more efficiently usable map view. While the footprint in this example is a simple square, in general, the map tool may operate on any shape of footprint.

Detailed Description Considerations

In the following detailed description, numerous details are set forth to provide a thorough understanding of the claimed subject matter. However, it will be understood by those skilled in the art that the claimed subject matter may be practiced without these specific details. In other instances, methods, apparatus or systems that would be known by one of ordinary skill have not been described in detail so as not to obscure claimed subject matter.

It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the present invention. The first contact and the second contact are both contacts, but they are not the same contact.

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of mobile devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), may also be used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). In some embodiments, the device is a gaming computer with orientation sensors (e.g., orientation sensors in a gaming controller).

In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device may include one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

The various applications that may be executed on the device may use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device may support the variety of applications with user interfaces that are intuitive and transparent to the user.

Some portions of the detailed description which follow are presented in terms of algorithms or symbolic representations of operations on binary digital signals stored within a memory of a specific apparatus or special purpose computing device or platform. In the context of this particular specification, the term specific apparatus or the like includes a general purpose computer once it is programmed to perform particular functions pursuant to instructions from program software. Algorithmic descriptions or symbolic representations are examples of techniques used by those of ordinary skill in the signal processing or related arts to convey the substance of their work to others skilled in the art. An algorithm is here, and is generally, considered to be a self-consistent sequence of operations or similar signal processing leading to a desired result. In this context, operations or processing involve physical manipulation of physical quantities. Typically, although not necessarily, such quantities may take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared or otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals or the like. It should be understood, however, that all of these or similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as apparent from the following discussion, it is appreciated that throughout this specification discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining”, or the like refer to actions or processes of a specific apparatus, such as a special purpose computer or a similar special purpose electronic computing device. In the context of this specification, therefore, a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device.

Example Mobile Device

Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable mobile device 100 with touch-sensitive displays 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience, and may also be known as or called a touch-sensitive display system. Device 100 may include memory 102 (which may include one or more computer-readable storage mediums, including non-transitory computer-readable storage mediums), memory controller 122, one or more processing units (CPU's) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input or control devices 116, and external port 124. Device 100 may include one or more optical sensors 164. These components may communicate over one or more communication buses or signal lines 103.

It should be appreciated that device 100 is only one example of a portable mobile device, and that device 100 may have more or fewer components than shown, may combine two or more components, or may have a different configuration or arrangement of the components. The various components shown in FIG. 1A may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits.

Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU 120 and the peripherals interface 118, may be controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use any of multiple communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2). The headset jack provides an interface between audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 may include display controller 156 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input control devices 116 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) may include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons may include a push button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of multiple touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 may capture still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device, so that the touch screen display may be used as a viewfinder for still and/or video image acquisition. In some embodiments, another optical sensor is located on the front of the device so that the user's image may be obtained for videoconferencing while the user views the other video conference participants on the touch screen display.

Device 100 may also include one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 may be coupled to input controller 160 in I/O subsystem 106. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the mobile device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 includes one or more orientation sensors 168. In some embodiments, the one or more orientation sensors include one or more accelerometers (e.g., one or more linear accelerometers and/or one or more rotational accelerometers). In some embodiments, the one or more orientation sensors include one or more gyroscopes. In some embodiments, the one or more orientation sensors include one or more magnetometers. In some embodiments, the one or more orientation sensors include one or more of global positioning system (GPS), Global Navigation Satellite System (GLONASS), and/or other global navigation system receivers. The GPS, GLONASS, and/or other global navigation system receivers may be used for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100. In some embodiments, the one or more orientation sensors include any combination of orientation/rotation sensors. FIG. 1A shows the one or more orientation sensors 168 coupled to peripherals interface 118. Alternately, the one or more orientation sensors 168 may be coupled to an input controller 160 in I/O subsystem 106. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more orientation sensors.

In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments memory 102 stores device/global internal state 157, as shown in FIGS. 1A and 3. Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information concerning the device's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 may detect contact with touch screen 112 (in conjunction with display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, may include determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

Contact/motion module 130 may detect a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, a gesture may be detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. In some embodiments, a gesture may be detected through a camera directed at a user's hand, where the gesture is performed without contact on the screen of the mobile device.

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic may be assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact         list);     -   telephone module 138;     -   video conferencing module 139;     -   e-mail client module 140;     -   instant messaging (IM) module 141;     -   workout support module 142;     -   camera module 143 for still and/or video images;     -   image management module 144;     -   browser module 147;     -   calendar module 148;     -   widget modules 149, which may include one or more of: weather         widget 149-1, stocks widget 149-2, calculator widget 149-3,         alarm clock widget 149-4, dictionary widget 149-5, and other         widgets obtained by the user, as well as user-created widgets         149-6;     -   widget creator module 150 for making user-created widgets 149-6;     -   search module 151;     -   video and music player module 152, which may be made up of a         video player     -   module and a music player module;     -   notes module 153;     -   map module 154; and/or     -   online video module 155.

Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of multiple communications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 1493, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.

Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 may store a subset of the modules and data structures identified above. Furthermore, memory 102 may store additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.

The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that may be displayed on device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, orientation sensor(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.

Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.

Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.

In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.

Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, includes a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, includes a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1.

For example, object updater 176 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate mobile devices 100 with input-devices, not all of which are initiated on touch screens, e.g., coordinating mouse movement and mouse button presses with or without single or multiple keyboard presses or holds, user movements taps, drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of the device, oral instructions, detected eye movements, biometric inputs, and/or any combination thereof, which may be utilized as inputs corresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable mobile device 100 having a touch screen 112 in accordance with some embodiments. The touch screen may display one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user may select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture may include one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some embodiments, inadvertent contact with a graphic may not select the graphic. For example, a swipe gesture that sweeps over an application icon may not select the corresponding application when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also may accept verbal input for activation or deactivation of some functions through microphone 113.

It should be noted that, although many of the following examples will be given with reference to inputs on touch screen 112 (where the touch sensitive surface and the display are combined), a touch-sensitive surface that is separate from the display may be used instead of touch screen 112.

Map Service Operating Environment

Various embodiments of a map tool may operate within a map service operating environment. FIG. 3 illustrates a map service operating environment, according to some embodiments. A map service 380 may provide map services for one or more client devices 352 a-352 c in communication with the map service 380 through various communication methods and protocols. A map service 380 generally may provide map information and other map-related data, such as two-dimensional map image data (e.g., aerial view of roads utilizing satellite imagery), three-dimensional map image data (e.g., traversable map with three-dimensional features, such as buildings), route and direction calculation (e.g., ferry route calculations or directions between two points for a pedestrian), real-time navigation data (e.g., turn-by-turn visual navigation data in two or three dimensions), location data (e.g., where is the client device currently located), and other geographic data (e.g., wireless network coverage, weather, traffic information, or nearby points-of-interest). In various embodiments, the map service data may include localized labels for different countries or regions; localized labels may be utilized to present map labels (e.g., street names, city names, points of interest) in different languages on client devices. Client devices 352 a-352 c may utilize these map services by obtaining map service data. Client devices 352 a-352 c may implement various techniques to process map service data. Client devices 352 a-352 c may then provide map services to various entities, including, but not limited to, users, internal software or hardware modules, and/or other systems or devices external to the client devices 352 a-352 c.

In some embodiments, a map service may be implemented by one or more nodes in a distributed computing system. Each node may be assigned one or more services or components of a map service. Some nodes may be assigned the same map service or component of a map service. A load balancing node may distribute access or requests to other nodes within a map service. In some embodiments a map service may be implemented as a single system, such as a single server. Different modules or hardware devices within a server may implement one or more of the various services provided by a map service.

A map service may provide map services by generating map service data in various formats. In some embodiments, one format of map service data may be map image data. Map image data may provide image data to a client device so that the client device may process the image data (e.g., rendering and/or displaying the image data as a two-dimensional or three-dimensional map). Map image data, whether in two or three dimensions, may specify one or more map tiles. A map tile may be a portion of a larger map image. Assembling together the map tiles of a map may produce the original map. Tiles may be generated from map image data, routing or navigation data, or any other map service data. In some embodiments map tiles may be raster-based map tiles, with tile sizes ranging from any size both larger and smaller than a commonly-used 256 pixel by 256 pixel tile. Raster-based map tiles may be encoded in any number of standard digital image representations including, but not limited to, Bitmap (.bmp), Graphics Interchange Format (.gif), Joint Photographic Experts Group (.jpg, .jpeg, etc.), Portable Networks Graphic (.png), or Tagged Image File Format (.tiff). In some embodiments, map tiles may be vector-based map tiles, encoded using vector graphics, including, but not limited to, Scalable Vector Graphics (.svg) or a Drawing File (.drw). Embodiments may also include tiles with a combination of vector and raster data. Metadata or other information pertaining to the map tile may also be included within or along with a map tile, providing further map service data to a client device. In various embodiments, a map tile may be encoded for transport utilizing various standards and/or protocols, some of which are described in examples below.

In various embodiments, map tiles may be constructed from image data of different resolutions depending on zoom level. For instance, for low zoom level (e.g., world or globe view), the resolution of map or image data need not be as high relative to the resolution at a high zoom level (e.g., city or street level). For example, when in a globe view, there may be no need to render street level artifacts as such objects would be so small as to be negligible in many cases.

A map service may perform various techniques to analyze a map tile before encoding the tile for transport. This analysis may optimize map service performance for both client devices and a map service. In some embodiments map tiles may be analyzed for complexity, according to vector-based graphic techniques, and constructed utilizing complex and non-complex layers. Map tiles may also be analyzed for common image data or patterns that may be rendered as image textures and constructed by relying on image masks. In some embodiments, raster-based image data in a map tile may contain certain mask values, which are associated with one or more textures. Embodiments may also analyze map tiles for specified features that may be associated with certain map styles that contain style identifiers.

Other map services may generate map service data relying upon various data formats separate from a map tile. For example, map services that provide location data may utilize data formats conforming to location service protocols, such as, but not limited to, Radio Resource Location services Protocol (RRLP), TIA 801 for Code Division Multiple Access (CDMA), Radio Resource Control (RRC) position protocol, or LTE Positioning Protocol (LPP). Embodiments may also receive or request data from client devices identifying device capabilities or attributes (e.g., hardware specifications or operating system version) or communication capabilities (e.g., device communication bandwidth as determined by wireless signal strength or wire or wireless network type).

A map service may obtain map service data from internal or external sources. For example, satellite imagery used in map image data may be obtained from external services, or internal systems, storage devices, or nodes. Other examples may include, but are not limited to, GPS assistance servers, wireless network coverage databases, business or personal directories, weather data, government information (e.g., construction updates or road name changes), or traffic reports. Some embodiments of a map service may update map service data (e.g., wireless network coverage) for analyzing future requests from client devices.

Various embodiments of a map service may respond to client device requests for map services. These requests may be a request for a specific map or portion of a map. Embodiments may format requests for a map as requests for certain map tiles. In some embodiments, requests may also supply the map service with starting locations (or current locations) and destination locations for a route calculation. A client device may also request map service rendering information, such as map textures or stylesheets. In at least some embodiments, requests may also be one of a series of requests implementing turn-by-turn navigation. Requests for other geographic data may include, but are not limited to, current location, wireless network coverage, weather, traffic information, or nearby points-of-interest.

A map service may, in some embodiments, may analyze client device requests to optimize a device or map service operation. For example, a map service may recognize that the location of a client device is in an area of poor communications (e.g., weak wireless signal) and send more map service data to supply a client device in the event of loss in communication or send instructions to utilize different client hardware (e.g., orientation sensors) or software (e.g., utilize wireless location services or Wi-Fi positioning instead of GPS-based services). In another example, a map service may analyze a client device request for vector-based map image data and determine that raster-based map data better optimizes the map image data according to the image's complexity. Embodiments of other map services may perform similar analysis on client device requests and as such the above examples are not intended to be limiting.

Various embodiments of client devices (e.g., client devices 352 a-352 c) may be implemented on different device types. Examples of a portable-mobile device include the devices illustrated in FIGS. 1 through 3 and 9, such as mobile device 100 and mobile device 300. Client devices 352 a-352 c may utilize map service 380 through various communication methods and protocols described below. In some embodiments, client devices 352 a-352 c may obtain map service data from map service 380. Client devices 352 a-352 c may request or receive map service data. Client devices 352 a-352 c may then process map service data (e.g., render and/or display the data) and may send the data to another software or hardware module on the device or to an external device or system.

A client device may, according to some embodiments, implement techniques to render and/or display maps. These maps may be requested or received in various formats, such as map tiles described above. A client device may render a map in two-dimensional or three-dimensional views. Some embodiments of a client device may display a rendered map and allow a user, system, or device providing input to manipulate a virtual camera in the map, changing the map display according to the virtual camera's position, orientation, and field-of-view. Various forms and input devices may be implemented to manipulate a virtual camera. In some embodiments, touch input, through certain single or combination gestures (e.g., touch-and-hold or a swipe) may manipulate the virtual camera. Other embodiments may allow manipulation of the device's physical location to manipulate a virtual camera. For example, a client device may be tilted up from its current position to manipulate the virtual camera to rotate up. In another example, a client device may be tilted forward from its current position to move the virtual camera forward. Other input devices to the client device may be implemented including, but not limited to, auditory input (e.g., spoken words), a physical keyboard, mouse, and/or a joystick.

Embodiments may provide various visual feedback to virtual camera manipulations, such as displaying an animation of possible virtual camera manipulations when transitioning from two-dimensional map views to three-dimensional map views. Embodiments may also allow input to select a map feature or object (e.g., a building) and highlight the object, producing a blur effect that maintains the virtual camera's perception of three-dimensional space.

In some embodiments, a client device may implement a navigation system (e.g., turn-by-turn navigation). A navigation system provides directions or route information, which may be displayed to a user. Embodiments of a client device may request directions or a route calculation from a map service. A client device may receive map image data and route data from a map service. In some embodiments, a client device may implement a turn-by-turn navigation system, which provides real-time route and direction information based upon location information and route information received from a map service and/or other location system, such as Global Positioning Satellite (GPS). A client device may display map image data that reflects the current location of the client device and update the map image data in real-time. A navigation system may provide auditory or visual directions to follow a certain route.

A virtual camera may be implemented to manipulate navigation map data according to some embodiments. Some embodiments of client devices may allow the device to adjust the virtual camera display orientation to bias toward the route destination. Embodiments may also allow virtual camera to navigation turns simulating the inertial motion of the virtual camera.

Client devices may implement various techniques to utilize map service data from map service. Embodiments may implement some techniques to optimize rendering of two-dimensional and three-dimensional map image data. In some embodiments, a client device may locally store rendering information. For example, a client may store a stylesheet which provides rendering directions for image data containing style identifiers. In another example, common image textures may be stored to decrease the amount of map image data transferred from a map service. Client devices may also implement various modeling techniques to render two-dimensional and three-dimensional map image data, examples of which include, but are not limited to: generating three-dimensional buildings out of two-dimensional building footprint data; modeling two-dimensional and three-dimensional map objects to determine the client device communication environment; generating models to determine whether map labels are seen from a certain virtual camera position; and generating models to smooth transitions between map image data. Some embodiments of client devices may also order or prioritize map service data in certain techniques. For example, a client device may detect the motion or velocity of a virtual camera, which if exceeding certain threshold values, lower-detail image data will be loaded and rendered of certain areas. Other examples include: rendering vector-based curves as a series of points, preloading map image data for areas of poor communication with a map service, adapting textures based on display zoom level, or rendering map image data according to complexity.

In some embodiments, client devices may communicate utilizing various data formats separate from a map tile. For example, some client devices may implement Assisted Global Positioning Satellites (A-GPS) and communicate with location services that utilize data formats conforming to location service protocols, such as, but not limited to, Radio Resource Location services Protocol (RRLP), TIA 801 for Code Division Multiple Access (CDMA), Radio Resource Control (RRC) position protocol, or LTE Positioning Protocol (LPP). Client devices may also receive GPS signals directly. Embodiments may also send data, with or without solicitation from a map service, identifying the client device's capabilities or attributes (e.g., hardware specifications or operating system version) or communication capabilities (e.g., device communication bandwidth as determined by wireless signal strength or wire or wireless network type).

FIG. 3 illustrates one possible embodiment of an operating environment 399 for a map service 380 and client devices 352 a-352 c. In some embodiments, devices 352 a, 352 b, and 352 c can communicate over one or more wire or wireless networks 360. For example, wireless network 360, such as a cellular network, can communicate with a wide area network (WAN) 370, such as the Internet, by use of gateway 364. A gateway 364 may provide a packet oriented mobile data service, such as General Packet Radio Service (GPRS), or other mobile data service allowing wireless networks to transmit data to other networks, such as wide area network 370. Likewise, access device 362 (e.g., IEEE 802.11g wireless access device) can provide communication access to WAN 370. Devices 352 a and 352 b can be any portable electronic or computing device capable of communicating with a map service, such as a portable mobile device described below with respect to FIGS. 1 to 3 and 9. Device 352 c can be any non-portable electronic or computing device capable of communicating with a map service, such as a system described below in FIG. 3.

In some embodiments, both voice and data communications can be established over wireless network 360 and access device 362. For example, device 352 a can place and receive phone calls (e.g., using voice over Internet Protocol (VoIP) protocols), send and receive e-mail messages (e.g., using Simple Mail Transfer Protocol (SMTP) or Post Office Protocol 3 (POP3)), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over wireless network 360, gateway 364, and WAN 370 (e.g., using Transmission Control Protocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)). Likewise, in some implementations, devices 352 b and 352 c can place and receive phone calls, send and receive e-mail messages, and retrieve electronic documents over access device 362 and WAN 370. In various embodiments, any of the illustrated client device may communicate with map service 380 and/or other service(s) 382 using a persistent connection established in accordance with one or more security protocols, such as the Secure Sockets Layer (SSL) protocol or the Transport Layer Security (TLS) protocol.

Devices 352 a and 352 b can also establish communications by other means. For example, wireless device 352 a can communicate with other wireless devices (e.g., other devices 352 a or 352 b, cell phones) over the wireless network 360. Likewise devices 352 a and 352 b can establish peer-to-peer communications 392 (e.g., a personal area network) by use of one or more communication subsystems, such as Bluetooth® communication from Bluetooth Special Interest Group, Inc. of Kirkland, Wash. 352 c can also establish peer to peer communications with devices 352 a or 352 b. (not pictured). Other communication protocols and topologies can also be implemented. Devices 352 a and 352 b may also receive Global Positioning Satellite (GPS) signals from GPS 390.

Devices 352 a, 352 b, and 352 c can communicate with map service 380 over the one or more wire and/or wireless networks, 360 or 362. For example, map service 380 can provide a map service data to rendering devices 352 a, 352 b, and 352 c. Map service 380 may also communicate with other services 382 to obtain data to implement map services. Map service 380 and other services 382 may also receive GPS signals from GPS 390.

In various embodiments, map service 380 and/or other service(s) 382 may be configured to process search requests from any of client devices. Search requests may include but are not limited to queries for business, address, residential locations, points of interest, or some combination thereof. Map service 380 and/or other service(s) 382 may be configured to return results related to a variety of parameters including but not limited to a location entered into an address bar or other text entry field (including abbreviations and/or other shorthand notation), a current map view (e.g., user may be viewing one location on the mobile device while residing in another location), current location of the user (e.g., in cases where the current map view did not include search results), and the current route (if any). In various embodiments, these parameters may affect the composition of the search results (and/or the ordering of the search results) based on different priority weightings. In various embodiments, the search results that are returned may be a subset of results selected based on specific criteria include but not limited to a quantity of times the search result (e.g., a particular point of interest) has been requested, a measure of quality associated with the search result (e.g., highest user or editorial review rating), and/or the volume of reviews for the search results (e.g., the number of times the search result has been review or rated).

In various embodiments, map service 380 and/or other service(s) 382 may be configured to provide auto-complete search results that may be displayed on the client device, such as within the mapping application. For instance, auto-complete search results may populate a portion of the screen as the user enters one or more search keywords on the mobile device. In some cases, this feature may save the user time as the desired search result may be displayed before the user enters the full search query. In various embodiments, the auto complete search results may be search results found by the client on the client device (e.g., bookmarks or contacts), search results found elsewhere (e.g., from the internet) by map service 380 and/or other service(s) 382, and/or some combination thereof. As is the case with commands, any of the search queries may be entered by the user via voice or through typing. The mobile device may be configured to display search results graphically within any of the map display described herein. For instance, a pin or other graphical indicator may specify locations of search results as points of interest. In various embodiments, responsive to a user selection of one of these points of interest (e.g., a touch selection, such as a tap), the mobile device may be configured to display additional information about the selected point of interest including but not limited to ratings, reviews or review snippets, hours of operation, store status (e.g., open for business, permanently closed, etc.), and/or images of a storefront for the point of interest. In various embodiments, any of this information may be displayed on a graphical information card that is displayed in response to the user's selection of the point of interest.

In various embodiments, map service 380 and/or other service(s) 382 may provide one or more feedback mechanisms to receive feedback from client devices 352 a-c. For instance, client devices may provide feedback on search results to map service 380 and/or other service(s) 382 (e.g., feedback specifying ratings, reviews, temporary or permanent business closures, errors etc.); this feedback may be used to update information about points of interest in order to provide more accurate or more up-to-date search results in the future. In some embodiments, map service 380 and/or other service(s) 382 may provide testing information to the client device (e.g., an A/B test) to determine which search results are best. For instance, at random intervals, the client device may receive and present two search results to a user and allow the user to indicate the best result. The client device may report the test results to map service 380 and/or other service(s) 382 to improve future search results based on the chosen testing technique, such as an A/B test technique in which a baseline control sample is compared to a variety of single-variable test samples in order to improve results.

Example Mapping Functionality

FIG. 3 illustrates another example of a mobile device that may implement a map tool in accord with the embodiments described, where the mobile device may be configured in a manner similar to the mobile device described above. In the illustrated embodiment, a mobile device 300 includes a mapping application (e.g., map module 154 described above) that may be stored in one or more memories of mobile device 300 and executed on one or more processors of mobile device 300. As is the case for the mobile device described above, mobile device 300 may include one or more controls 302 for operating the mobile device. These controls may include but are not limited to power controls for turning the device on and off, volume controls for adjusting the ear piece volume or the speaker volume, menu controls for navigation functions of the device, and function controls for initiating one or more function or actions on the device. Controls 302 may include hardware controls or software controls. For instance, the bottom left corner of electronic display 312 includes a graphical representation of a control 312 that may be selected by a user, such as by way of touch in accordance with the touch screen functionality described above.

Mobile device 300 may also include other components similar to those described above, such as a microphone 304, an earpiece 306 (e.g., a speaker through which to convey audio representations of telephone calls), an optical sensor 308, and/or a speaker 310. Each of these components may be configured in a similar manner to those like-named components of FIG. 2 described above. Furthermore, electronic display 312 may be configured with touch screen capability, such as touch screen 112 described above. In various embodiments, controls (e.g., on screen control(s) 302) may be utilized to perform any of a variety of map-related functions including but not limited to zoom in, zoom out, rotate screen, pan screen, toggle views (e.g., two-dimensions to three dimensions and vice versa), and/or another map related activity. In various embodiments, one or more gestures may be utilized to perform any of the aforesaid map controls (with or without the use of an actual graphical on-screen control). In one non-limiting example, a one figure gesture may be utilized to adjust the pitch within a three-dimensional map view.

As noted above, mobile device 300 includes a mapping application that may be stored in one or more memories of mobile device 300 and executed on one or more processors of mobile device 300. In the illustrated embodiment, the graphical representation of the mapping application may include a map 314 of a geographic region. This map may be presented as a two-dimensional map or a three-dimensional map, the selection of which may be specified through, e.g., a user-configurable parameter of the mapping application. In some embodiments, the mobile device may toggle between two-dimensional map or three-dimensional map views responsive to input from any input component of the mobile device. In one non-limiting example, input from orientation sensor(s) 168 may initiate the transition from a two-dimensional map view to a three-dimensional map, and vice versa. For instance, one or more of orientation sensor(s) 168 may detect a tilt (e.g., a user-initiated tilt) in the orientation of the mobile device and, in response, initiate the aforesaid toggling.

Map 314 may include a graphical position indicator 316, which may represent the location of the mobile device within the geographic region of the map. Generally position indicator 316 may represent the current or real-time position of the mobile device, although it should be understood that in some cases there may exist some small amount of temporal latency between the actual position of the mobile device and the graphical representation of that location (e.g., position indicator 316). This may occur, e.g., when the mobile device is in motion. In various embodiments, the mobile device may be configured to perform map matching including but not limited to aligning a sequence of observed user positions with a road network on a digital map. In various embodiments, the mobile device may be configured to perform a “snap to” function in which the graphical position indicator 316 is aligned onto a roadway when the user's position falls within in a specified threshold distance of the roadway.

Furthermore, mobile device 300 may generally be operated by a user. For example, mobile device 300 may in some cases be a smartphone utilized by an individual to make phone calls, send text messages, browse the internet, etc. As use of mobile device by an individual generally implies the individual is proximate to the mobile device (e.g., the user may be holding the device in his or her hand), references herein to the location of the device and the location of the user may be considered to be synonymous. However, it should be understood that in some cases the actual position of the mobile device and the user of that device may differ by some distance. For instance, the user may place his or her mobile device on a table of an outdoor café while sitting in a nearby chair. In this case, the position of the device and the position of the user may differ by some small amount. In another example, mobile device 300 may be mounted on a car dashboard (e.g., for use as a navigation device) while the user of the device sits nearby (e.g., in the driver seat of the car). In this case as well, the position of the device and the position of the user may differ by some small amount. Despite these small differences in position, generally the position of the mobile device and the position of the mobile device user may be considered to coincide.

In various embodiments, the map 314 displayed by the mobile device may include one or more roads (e.g., roads 318 a-b), buildings (not illustrated), terrain features (e.g., hills, mountains) (not illustrated), parks (not illustrated), water bodies (not illustrated), and/or any other item that may be conveyed by a map. In some cases, the map may also include other map or navigation information including but limited to readouts from one or more of a directional compass, an altimeter, and/or a thermometer.

In various embodiments, the mapping application may be configured to generate directions from an origination (e.g., an address or a user's current position) to a destination (e.g., an address, landmark, bookmarked/saved location, or point of interest). For instance, an indication of the origination and/or destination may be input into the multi function device by the user. The mobile device may generate one or more candidate routes between those two points. The mobile device may select one of those routes for display on the device. In other cases, multiple candidate routes may be presented to the user and the user may select a preferred route. In the illustrated embodiment, one route is illustrated as route 320. The route may also include turn-by-turn directions which may be presented to the user (in 2D or 3D), such as a graphical indication to perform a turn 322 a from road 318 a to road 318 b. In some embodiments, this graphical indication to perform a turn may be supplemented or substituted with an audible indication to turn, such as a voice command from speaker 310 that indicates the user is to “turn left in 100 yards,” for example. In some embodiments, the route that is selected may be presented to the user as a route overview. For instance, before proceeding with navigation, the mobile device may generate a route overview display that graphically indicates key information for the route, such as key turns, route distance and/or an estimated time for traversing the route. In some cases, the mobile device may be configured to generate a display of driving maneuvers (e.g., turns, lane changes, etc.) that occur in quick succession, either in the route overview or during actual navigation. This information may help the user safely prepare for such maneuvers. In some cases, the route information may be presented in a list format, such as a list of turns or other maneuvers.

In various embodiments, the mapping application of the mobile device may be configured to track the position of the user over time and correspondingly adjust the graphical position indicator 316 to indicate the new position. For instance, the mapping application may determine that the user is traveling along route 320 from position information (e.g., information from GPS module 135) and update the map 314 accordingly. For instance, in some cases the map 314 may remain stationary while position indicator 316 is moved along the route. In other cases, position indicator 316 may remain stationary or “fixed” while map 314 is moved (e.g., panned, turned, etc.) around the position indicator.

In various embodiments, the mobile device may be configured to display alternate or contingency routes. In some cases, these routes may be selectable by the user (e.g., via the touch screen interface). In other cases, the mobile device may select a best route based on one or more parameters, such as shortest distance or time. In some cases, these parameters or preferences may be set by the user.

As described in more detail below, the mobile device may in various embodiments receive routing information that specifies a route from a map service. In some case, the mobile device may carry out navigation guidance in accordance with this route. However, in some cases, the mobile device may perform a reroute operation in order to generate a new route to the destination. For instance, the user may have deviated from the original route or explicitly requested a new route. In some cases, the mobile device may perform rerouting based on cached map data stored on the mobile device.

In various embodiments, the mobile device may be configured to perform route correction based on real-time data, such as updates in map information, road conditions, traffic conditions, and/or weather conditions. For instance, the mobile device may be configured to alter a route such that the route avoids a construction zone or a dangerous storm cell.

In various embodiments, the mobile device may be configured to perform lane guidance independently or as part of navigation guidance. For instance, the mobile device may, in response to detecting that multiple turns follow in quick succession, provide the user with a direction or suggestion as to which lane to occupy. For instance, a voice or visual indication may specify that the user “turn right, then move to the left lane” in anticipation of a subsequent left turn. In another example, the mobile device may detect one or more lane closures (e.g., due to construction or other reasons) and instruct the user to avoid such lanes.

In various embodiments, the mobile device may be configured to generate voice prompts for directions. For instance, during navigation guidance, the mobile device may be configured to generate audio representations of the next turn or driving maneuver on the route. For instance, the mobile device may be configured to audibly indicate the user should “turn left in 100 yards” or some other audible indication of a maneuver.

In various embodiments, the mobile device may be responsive to various voice commands for performing actions including a command to obtain a route. For instance, the mobile device may interpret the user's voice through a microphone or other transducer of the mobile device. The user may specify an origination and a destination for the requested route. In various embodiments, the mobile device may be configured to utilize the user's current location as the origination for the route.

In various embodiments, the mobile device may be configured to perform a search along a specific route, such as current navigation route. For instance, the user of the mobile device may request the location of points of interest, such as fuel stations or restaurants. However, if a user is traveling along a particular route, they may not be particularly interested in points of interest that are not proximate to that route. As such, the mobile device may be configured to scope any searches to points of interested within a specified distance away from the route. In various embodiments, this distance may be a configurable parameter.

In various embodiments, the mobile device may be configured to display various graphical layers including but not limited to a graphical map information, aerial images (e.g., plane, dirigible, helicopter-mounted cameras, satellite-acquired images), and/or traffic information. For instance, in the traffic information example, the mobile device may overlay color coded traffic information on roadways to indicate the speed at which traffic is flowing. For example, green color coding may be used to indicate traffic is flowing normally, and yellow or red may be used to indicate traffic slowdowns.

In various embodiments, the mobile device may be configured to display any quantity of metrics or statistics about a navigation route including but not limited to an estimated time of arrival, travel distance remaining, average speed (overall or moving average), top speed, and/or other route statistics.

In various embodiments, the mobile device may be configured to display routes at different angles in order to accommodate the preferences of different users. Such viewing angles may include a birds eye view for two-dimensional maps to any of a variety of camera angles available for a three-dimensional map.

In various embodiments, the mobile device may be configured to provide navigation information other than map and routing information. For instance the mobile device may expose output from any of the hardware device described above with respect to FIG. 1. In one non-limiting example, an orientation sensor 168 may include a compass that outputs direction data. The mobile device described herein may be configured to display this directional data as a virtual compass, for example.

Example Roof Analysis Tool

FIGS. 4A-4D are flowcharts depicting selected processing stages of embodiments of a roof analysis tool operable on a server, such as map services 380 or other services 382. FIG. 4E is a flowchart depicting selected processing steps for an embodiments of a map tool, where the map tool is operable with a mapping application on a mobile device, and where the mapping application, as discussed above, may be invoked through the a user selecting the mapping application through the interface of a mobile device 300. The mapping application may engage the services of the map service operating system as described in regard to FIG. 3.

As per FIG. 4A, in some embodiments, a roof analysis tool, may access footprint data for one or more structures or buildings within a map region, as reflected in stage 402. In some cases, the footprint data may be two-dimensional mapping data that may use a geodetic (latitude and longitude) reference frame. In addition to the two-dimensional data, the roof analysis tool may have access to three-dimensional data set that corresponds to the same map region as corresponds to the two-dimensional data. In some cases the three-dimensional data may be vector-based mesh data composed of multiple triangles representative of various surfaces within the map region. From the three-dimensional data set corresponding to the map region and based on the footprint data for a structure of the one or more structures within the map region, the roof analysis tool may identify multiple points on a roof of a structure, as reflected in stage 404.

For example, to identify the multiple points on the roof of the given structure, the roof analysis tool may correlate coordinates for a given footprint with coordinates within the mesh data in order to identify the mesh data corresponding to the footprint. Once the mesh data for the footprint is identified or extracted, the roof analysis tool may determine the highest points within the footprint, where the highest points are determined to be points on a roof of the structure with the given footprint. Further, the points may correspond to vertices of triangles representing the roof of the structure.

The roof analysis tool may then calculate, based on the multiple points on the roof of the structure, multiple groups of normals, as reflected in stage 406. To identify the groups of normals, the roof analysis tool may first calculate a normal for each of the points identified, where the normal is represented in three-dimensional Cartesian coordinates, and where the normal is perpendicular to the surface of the roof. The roof analysis too may then transform the normal from three-dimensional Cartesian coordinates into spherical coordinates for a unit sphere. The roof analysis tool may then repeat this process to generate a normal for each of the points on the roof of the structure. Because a normal projects perpendicularly out from the surface of the roof of the structure, the normals for a plane for one plane of the roof should all be pointing in roughly the same direction, accounting for some noise in the three-dimensional data set.

Given the multiple calculated normals, the roof analysis tool may determine which groups of normals point in roughly the same direction. In this example, the roof analysis tool performs a Hough transformation on the normals as represented by their respective spherical coordinates. A result of the Hough transformation is a two-dimensional histogram, where one axis corresponds to the rho angle of the spherical coordinates for a normal and another axis corresponds to the psi angle of the spherical coordinates for the normal. In this example, the rho angle ranges 180 degrees (−90 to +90 degrees) and the psi angle ranges from 0-180. Using the two-dimensional histogram, the roof analysis tool may identify clusters, which correspond to groups of normals, and the roof analysis tool may determine a normal for the group of normals based on an average normal of the cluster.

Using a respective average normal for a respective group of normals, the roof analysis tool may iterate over each of normals and determine to which of the average normals the current normal being considered is closest to, and the roof analysis tool may then classify that currently considered normal as part of a group of normals that correspond to the average normal which is closest to the currently considered normal.

Based on the average normal for the cluster, the roof analysis tool may determine the plane corresponding to the average normal, and where the corresponding plane is identified or determined to be a plane of the roof of the structure, as reflected in stage 408. The roof analysis tool may repeat the identification of planes in order to identify each of the planes corresponding to the planes of the roof of the structure.

Once each plane for the roof of the structure has been determined, the roof analysis tool may determine a parameter set for the roof of the structure based on parameter values describing each of the respective planes of the roof, as reflected in stage 410.

In some embodiments, the roof analysis tool may provide the parameter set describing each of the planes in a roof of a structure to a mobile device for the purpose of generating a three-dimensional map view that includes a rendering of the structure and the roof of the structure. In this example, the roof would be highly correlated to the actual shape of the actual structure within the map region.

In other embodiments, the roof analysis tool may instead use the parameter set describing a roof of the building to identify an archetypal roof style that may be similar to the actual shape of the of the actual structure within the map region. In other words, for a given archetypal roof style, say a hip and valley roof style, there may be many different shapes and arrangements of planes of a roof that would correspond to the archetypal roof style. Variations may be in the angles of the component planes of the roof, or in the length of one of the sections of the roof, among other variations. However, if the map view for the map region includes a rendering of a roof for a structure where the roof is of the same archetypal roof style as the actual structure, then the map view will bear a strong semblance of verisimilitude to the real world. In other words, the rendered roof in the map view, while not an exact match to the real world structure's roof, will be similar to the real world structure's roof.

To enable the embodiment of the roof analysis tool that provides an archetypal roof style for a building to a mobile device, the server may first provide the mobile device with a list of archetypal roof styles and with dimensions or parameters for how to render a given archetypal roof style in addition to an identification value for each of the archetypal roof styles. In this way, once the mobile device and the server implementing the roof analysis tool are synchronized, the mobile device may simply receive an archetypal identification value and identifying information for the building to which the archetypal identification value corresponds in order to determine which style of roof to render on top of a given building.

As per FIG. 4B, in some embodiments, a roof analysis tool, may access footprint data for one or more structures or buildings within a map region, as reflected in stage 422. In addition to the two-dimensional footprint data, the roof analysis tool may have access to three-dimensional data set that corresponds to the same map region as the two-dimensional data. From the three-dimensional data set corresponding to the map region and based on the footprint data for a structure of one or more structures within the map region, the roof analysis tool may identify multiple points on a roof of the structure, as reflected in stage 424.

The roof analysis tool may then calculate, based on the multiple points on the roof of the structure, multiple groups of normals, as reflected in stage 426. To identify the groups of normals, the roof analysis tool may first calculate a normal for each of the points identified, where the normal is represented in three-dimensional Cartesian coordinates, and where the normal is perpendicular to the surface of the roof. The roof analysis too may then transform the normal from three-dimensional Cartesian coordinates into spherical coordinates for a unit sphere. The roof analysis tool may then repeat this process to generate a normal for each of the points on the roof of the structure. Given each normal represented in spherical coordinates, the roof analysis tool may apply a transformation to the spherical coordinates of the normals in order to generate a two-dimensional histogram. From the two-dimensional histogram, the roof analysis tool may identify clusters of normals. In some embodiments, the roof analysis tool may, instead of spherical coordinates, use another coordinate system with which to perform each of the calculations described herein.

Based on the multiple calculated normals, the roof analysis tool may identify a roof type classification for the structure, as reflected in stage 428. The roof analysis tool may determine the roof type classification for the structure based on the orientation of each of the panes of the roof. In other words, if the clusters of normals correspond to two planes, and where the average normal of one plane is, for example, 100 degrees from the average normal of the second plane, then the roof analysis tool may determine that the roof type is a gable type roof, such as gable roof 708 in FIG. 7. In this example, a gable type roof may be determined from a range of degrees between the normals of two intersecting planes, such as 30 degrees to 130 degrees. Other ranges may be defined for classifying a gable type roof. Similarly, each of the archetypal roofs may be defined within tolerance factors for either the number of planes in the archetypal roof, or the angles at which the planes or normals for the planes intersect. In this example, the roof analysis tool may determine that the roof type classification for the roof of the structure in the map region is a gable type roof.

As per FIG. 4C, in some embodiments, a roof analysis tool, may receive, for a map region, three-dimensional mapping data including multiple triangles representing respective surface regions for one or more objects in the map region, as reflected in stage 442. From the three-dimensional mapping data, the roof analysis tool may identify a subset of all the triangles in the mapping data, where the subset of triangles correspond to a roof for a building in the map region, as reflected in stage 444. In some cases, the subset of triangles may be determined by correlating a coordinates for a footprint for the building with a corresponding area within the mapping data for the coordinates for the footprint. In some cases, the footprint data may be determined from two-dimensional mapping information corresponding to the same or at least an overlapping map region as for the three-dimensional mapping data. In some cases, the map region may be received from a mobile device requesting a compact data representation, or a parameterized set of values describing roofs for buildings in the map region.

The roof analysis tool may then calculate a normal for a surface of a triangle within the subset of triangles, where the normal is represented as a vector in three-dimensional Cartesian coordinates, as reflected in stage 446. The roof analysis tool may then transform the three-dimensional Cartesian coordinates for the calculated normal for the surface of the triangle into spherical coordinates for a unit sphere, as reflected in stage 448.

A problem that may arise when performing a Hough transformation on spherical coordinates for a flat roof is that the azimuth angles may range anywhere from 0-360 degrees due to noise in the three-dimensional mapping data. For example, for a flat roof, if the surface of the triangle on the roof is anything but perfectly perpendicular to the surface of the earth, then the slight degree of the normal from the perpendicular may exist in any direction. Therefore, to eliminate the range of azimuth angles in the spherical coordinates for the normal that are due to a range of z-axis values in the three-dimensional Cartesian coordinates for the normal, the roof analysis tool may transform the three-dimensional Cartesian coordinates of the normal into rho angle and psi angle parameters instead of theta angle and phi angle parameters, as reflected in stage 450. Examples of the rho and psi angles for an example normal may be seen in FIG. 6E, and rho angle 649 a and psi angle 649 b. Further, because roof normal directions point upward, and in the rho-psi parameterization, the range of the rho angle is limited to −90 and +90 degrees, and the range of the psi angle is 0-180 degrees.

The roof analysis tool may similarly process each of the remaining normals, and determine an archetypal roof classification based on groupings of normals as discussed above for FIG. 4B.

As per FIG. 4D, the roof analysis tool may identify, from a three-dimensional data set corresponding to a map region, multiple points on a roof of a structure within the map region, as reflected in stage 462. The roof analysis tool may determine the points on the roof of the structure in any of the methods discussed for other embodiments. The roof analysis tool may then calculate, based on the multiple points on the roof structure, multiple respective normals that are perpendicular to the roof of the structure, as reflected in stage 464, where the normal vector points away from the roof toward the sky.

The roof analysis tool may then cluster the multiple normals into multiple groups of normals, as reflected in stage 466. The clustering may be performed as discussed above in regard to FIG. 4A. For each respective group of normals within the multiple groups of normals, the roof analysis tool may identify a respective plane of the roof of the structure, as reflected in stage 468. For example, FIG. 6F illustrates several differently oriented flat roof surfaces that correspond to the normals illustrated in FIG. 6D, where the group of normals 630 corresponds to plane 650, and where group of normals 638 corresponds to plane 652. Further, in general, because of noise in the three-dimensional mesh data, there may be overlap between the planes, as illustrated in FIG. 6F.

Once each of the planes for a roof have been determined, for example, by determining three or more three-dimensional Cartesian coordinate points, one point for each corner of the plane, the roof analysis tool may identify a classification for a roof type, as reflected in stage 470. Further, the roof analysis tool may perform the identification of the classification of a roof type based on each of the respective planes determined to be part of the roof of the building. Example archetypal roof styles are depicted in FIG. 7 and hip and valley roof 702, gambrel roof 704, hip roof 706, gable roof 708, mansard roof 710, flat roof 712, and shed roof 714. However, this list of roof types is non-exhaustive, and a server implementing a roof analysis tool and a mobile device in communication with the server may synchronize on a common list of archetypal roofs that may include more or fewer than these seven example roof types.

Example Mobile Device Map Tool

As per FIG. 4E, and with regard to a mobile device such as mobile device 300, a map tool on the mobile device may display a three-dimensional view of a map, where the map tool bases the three-dimensional view on a three-dimensional model constructed from one or more data sets with mapping information corresponding to the map. The constructed three-dimensional model may include representations for buildings in the map region, as reflected in stage 482.

In some embodiments, the map tool on the mobile device may generate the three-dimensional model for all elements in a map region except for buildings. In this embodiment, when the map tool requests roof information from a server, the server provides the roof parameters for a given structure along with a height value for the structure. From this information for the structure, the map tool may render a building at the indicated height value, and with the indicated roof type, and with a building perimeter shape that matches the roof type perimeter in cases where the roof type information includes parameters for the shape of the roof. In cases where the parameters for the roof simply indicate a style, the shape of the building may be defined to match the footprint for the building, and a roof style matching the shape of the building is generated from the roof type classification.

However, for the embodiment where the map tool generates a three-dimensional model, the representations of the buildings in the map region for the three-dimensional model may only be extruded polygons, where the tops of the polygons are flat. Map view 500 in FIG. 5A is an example map view based on raster image data for a map region, and map view 502 in FIG. 5B is an example map view based on a constructed three-dimensional model of the same map region. Further, in map view 502, each of the buildings is an extruded polygon with a flat roof. However, not all of the actual roofs of the buildings corresponding to the extruded polygons have flat roofs.

To render a version of map view 502, but with roofs that approximate the roofs of the actual corresponding buildings, the mobile device may request and then receive, from a server implementing a roof analysis tool, a roof type classification corresponding to the buildings in the map region, as reflected in stage 484.

Based a roof type classification for a given building in the map and based on the three-dimensional model that includes a representation of the given building, the map tool on the mobile device may render a map view that has a rendered roof based on a respective roof type classification from among a list of multiple roof type classifications, as reflected in stage 486. For example, building 504 has a corresponding building in map view 500 that has a gable type roof; however, in map view 502, building 504 has a flat roof.

From the received roof type classifications from the server, the map tool on the mobile device may determine that building 504 corresponds to a gable type roof, where building 504 may be identified by coordinates within the map region and with an identification value for a roof type. Given only the parameter values that identify the building and that identify the roof type, the map tool on the mobile device may render a gable type roof for a more accurate map view of the map region.

In some embodiments, instead of the server providing the map tool on the mobile device with parameters identifying a building and a roof type corresponding to the building, the roof analysis tool on the server may provide the map tool with parameters describing the coordinates of various planes making up the roof for the building. For example, for the same building 504, the roof analysis tool on the server may provide the map tool on the mobile device with parameters including coordinates for the two planes of the gable roof. In this way, while still providing a compact parameterization of a roof because only coordinate values are transmitted, the map tool on the mobile device may render a roof for building 504 that is more accurate. The increased accuracy is because the pitch of the roof is reflected in the coordinates for the two planes whereas in the transmission of a roof classification type, the map tool may render a similar type roof for different buildings with the same type of roof even though the different buildings may have roofs with different pitches.

In some embodiments, the map tool on the mobile device may be designed to perform the functions described above in the various embodiments of a roof analysis tool. In other words, the use of the server by the map tool to provide roof parameters may provide increased responsiveness by the map tool because the server performs the calculations to identify the roof parameters, but the map tool may be capable of performing the same calculations.

In some embodiments, the map tool may simply assign random non-flat roof types to various buildings within a map view that have been classified/parameterized as being non-flat by the roof analysis tool in order to provide a better semblance of reality as compared to a map view including only flat roofs. In other cases, the map tool may randomly select a roof type from a list of roofs that correspond to particular zoning information. For example, for a residential zoning area, the map tool may randomly select a roof type for a building from among, for example, hip and valley, hip, or gable type roofs. However, for a commercially zoned area, the map tool may randomly select a roof type for a building from among, for example, flat, shed, or gable type roofs.

In some cases, the map tool may generate a three-dimensional model using elements from a two-dimensional data set of mapping information and from a three-dimensional data set of mapping information. For example, two-dimensional maps specifying locations and boundaries of various structures may be available to define the footprint of a given object or structure in a map area. In this example, three-dimensional mesh data corresponding to the map area may also be available, where within the highly-detailed set of data is information regarding heights of objects for a given location within the map area. The map tool may use the footprint for an object derived from the two-dimensional mapping information and extrude, or extend, the footprint into three-dimensional space using one or more height values, where the one or more height values correspond to one or more points within the footprint. In some cases, the height values are determined from three-dimensional mapping information. This process may be repeated for each object footprint in the map area, and once each object has been similarly processed, the result is a model of a three-dimensional space for the map area derived from multiple data sets from which a map view may be rendered.

An aspect of the three-dimensional model constructed from the two data sets is that the model may not accurately represent the shape of a given building. For example, if for a given footprint a single point in the center of the footprint were correlated to the corresponding point in the three-dimensional mapping information, the footprint for the object may be extruded to the height of the point. However, it may be the case that the top of the object may not be flat. In other words, if a given object has anything but a flat top, there may be multiple height values corresponding to different points within the object footprint. To compensate for the potential inaccuracy, the map tool may, in some cases, use multiple points to determine a height, or in some cases, determine multiple height values. While the constructed model may lack some accuracy, what is gained is a decrease in computational complexity.

In some embodiments, the map tool may generate a three-dimensional model using footprint data from a two-dimensional data set and a height value corresponding to the footprint. For example, the map tool may receive mapping information that includes coordinates for various footprints of various structures within a map region, and the mapping information may also include a single height value corresponding to each footprint. In this way, the map tool may, for each footprint in a map region, extrude a respective footprint within the map region according to a respective height value for the respective footprint. Once each footprint has been extruded, the map tool may render a three-dimensional map view representing the map region, where the three-dimensional map view is based on the extruded footprints within the map region.

Mobile devices may provide a user with map navigation that includes a three-dimensional view corresponding to a current position. In some cases, the three-dimensional view may be constructed based on Global Positioning System (GPS) data, map information from other sources, or based on GPS data combined with map information from other sources. In some cases, a map view may be constructed from map information corresponding to a given address or to some other piece of information from which location information may be derived. For example, from any point on earth, a user may give a voice command to the map tool, such as “show me the front of the Metropolitan Museum of Art in New York City.” In response to the voice command, the map tool, may access map information for the location of the Metropolitan Museum of Art in New York City and generate a map view to the user.

However, a map view presented to a user through a traditional mapping application on a mobile device may present a user with photographic detail of the surrounding environment. In some cases, the map view may include cars, buses, bicycles, bicycle riders, pedestrians, and other random objects, signs, or advertisements. A result may be a cluttered map view that may decrease the efficiency with which a user may navigate through the map area. Therefore, it may be beneficial, or more productive, for a user to have the option to see a simplified version of the surrounding environment so that information such as street names or prominent houses are more clearly conveyed. For example, a user may select a configuration setting to display, within a map view of a map application, an isometric view of structures drawn without texturing, or without any objects that are not structures. In some cases, a simplified map view may be a default setting, requiring no action from a user to enable.

In some embodiments, the map view provides a user with a bird's eye virtual camera view with photographic detail of the surrounding environment. In other embodiments, the map view provides a user with ground level virtual camera view from the perspective of the user's location within the displayed map area. In other embodiments, a user may choose the virtual camera perspective location from which the map view may be generated.

In some cases, the map view may be composed of various geometric figures and may be considered a low resolution proxy of the actual, or high resolution version of the surrounding environment. In either the bird's eye view, ground level view, or the isometric view of geometric figures, the map tool may use one or more sources of map information to construct the map view. In some cases, a data source containing of two-dimensional information may be combined with another data source containing three-dimensional information in order to generate a three-dimensional map view. In other cases, a three-dimensional source of mapping information alone may serve as a basis on which to construct a three-dimensional model of the surrounding environment.

In some cases, a user may manipulate a given map view such as through input indicating to the map tool to display a different virtual camera perspective of the map view. For example, within a given map view, a user may wish to see the map view from the other side of a building. However, given that the previously generated model of the map view has already been constructed, the map tool does not need to generate a new 3D model of the map view because the locations and spatial dimensions of object in the previously generated model remain valid for the new virtual camera perspective.

In an embodiment, three-dimensional (3D) data may be 3D mesh data, which may contain data defining the location and orientation of thousands of triangles for a given map view. Further in this embodiment, two-dimensional (2D) data may be obtained from maps for a given city or county which define the locations and the dimensions of footprints for structures, roads, sidewalks, plazas, or other objects. In this embodiment, in the interest of speed and computational complexity, a 3D proxy may be constructed through the transformation of the 2D model into a 3D model using selected pieces of information from the 3D model to enhance the 2D model. For example, if the 2D model provides information regarding the footprint of a given building, the map tool may then reference the 3D model to identify the corresponding location of the footprint of the building. Once the location of the footprint of the building is determined in the 3D model, one or more height values may be extracted from the 3D model for the building. Now, given the footprint of the building and the one or more height values, a rough box or polygon may be extruded to one of the height values, or to some value derived from the height values in order to generate an approximate 3D shape. This process may be repeated for each object in the 2D data, thereby creating a rough, low-resolution version of the surrounding environment.

In some embodiments, a single source of data may be used, for example, the 3D mesh data for the surrounding environment. In this example, a two-dimensional grid may be created, where each grid segment may be extruded based on a height value from the 3D mesh data, where the height value from the 3D mesh data is for a location corresponding to the grid segment. In the case where a given object in the map space overlaps with multiple grid segments, the display of adjacent grid segments may be smoothed into a contiguous three-dimensional object. In this way, a 3D model of the map space may be constructed using only height values extracted from the 3D mesh data.

In different embodiments, the map tool may adjust the granularity of the constructed 3D model based on various factors. For example, a user may choose a configuration setting to display different levels of detail in the 3D model, and in response, the map tool may construct the 3D model using additional information from the one or more source data sets of mapping information.

In some embodiments, a map tool on a mobile device, given multiple data sets of mapping information corresponding to a map or map area, may construct a three-dimensional model on which to base a map view to display. The map tool may receive two or more data sets of mapping information corresponding to a map region. In some cases, the mapping information is vector data and not raster image data.

Based on the received two or more data sets of mapping information, the map tool may determine one or more spatial dimensions for one or more objects in the map region. For example, the map tool may receive three-dimensional mapping information for the map region from Map Service 380 or from GPS 390. The map tool may also receive, from Map Service 380 or service 382 for example, two-dimensional mapping information that includes footprint information for buildings within the map region for which the three-dimensional mapping information corresponds. Further, the footprint may be the footprint of any object within the map region.

Given a footprint and the area of the map region in which the footprint exists, and given three-dimensional information corresponding to the map region, the map tool may determine one or more height values for the footprint. The map tool may use one or more points within the footprint, or points proximate to the footprint, and correlate the one or more points to respective one or more height values from the three-dimensional mapping information, where each respective height value corresponds to a respective point. In this way, the map tool may determine a height value for each of the points in the footprint. A result is that the map tool, based on two different data sets of mapping information, determines one or more spatial dimensions for one or more objects in the map region. In this example, spatial dimensions are determined from the two-dimensional mapping information (footprints) and spatial dimensions are determined from the three-dimensional mapping information (height values).

In some embodiments, a footprint may be divided into multiple regions, and height values may be correlated to the three-dimensional information for one or more locations within each of the regions. For example, a building may be L-shaped, where one leg of the L is not as tall as the other leg of the L. In this case, the footprint may be divided into two regions, one region corresponding to each leg of the L, and a height value for each region may be used as the basis for extruding the footprint into three dimensional space. The regions of the footprint may be determined in other manners, such as uniform division of the footprint into any given number of regions, for example, dividing each footprint into quarters.

Once the map tool has identified one or more height values corresponding to one or more points in a given footprint, the map tool may generate a three-dimensional version of the footprint. The map tool may generate an entire three-dimensional model based on the three-dimensional versions of each object footprint in the map region. For example, the map tool may extrude or extend the object footprint into three-dimensional space based on the height value. The generated three-dimensional model has a higher level of granularity than the two-dimensional mapping information in that the three-dimensional model includes height values in addition to the footprint information. The generated three-dimensional model also has a lower level of granularity than the three-dimensional mapping information in that the three-dimensional model does not have as much detail regarding the dimensions of objects within the map region. In other words, in this example, the generated three-dimensional model has a different level of granularity from each of the sets of mapping information on which the three-dimensional model is based.

The generated three-dimensional model may then serve as the basis for the generation of a display of the map area such as the map view in FIG. 5A. In some cases, the three-dimensional model may be augmented to include additional details, such as texture and shading for one or more objects within the three-dimensional model, or doors or windows or outlines of doors or windows. The additional details may be extracted from the mapping information already used, or the additional details may be based on another source of mapping information. For example, the map tool may use the cardinal direction of the user with respect to the current position of the sun to add accurate shading information to objects within the three-dimensional model. In other cases, the map tool may access a default settings file to apply default textures to various objects such as buildings or streets.

As discussed above, a simplified map view may provide a user with a more efficient map using experience. Overall, without distractions such as advertisements, vehicles, or people, the simplified map view is easier to comprehend and easier to navigate.

FIGS. 5A and 5B depict two versions of a map view of the same map area as depicted within screen area 312 of a mobile device. FIG. 5A depicts a rendering of three-dimensional digital surface model mesh data that was then “skinned” with rasterized texture data that was captured at the same time as the three-dimensional mesh. The depiction in FIG. 5A may be from a raster image taken, for example, from a satellite or helicopter. The photographic detail may provide a user with a general impression of the map area. However, with respect to navigation, a user may find the building details and cars a distraction. By contrast, the map view in FIG. 5B, based on a generated three-dimensional model, is aesthetically cleaner and simpler, and as a consequence, the street and building images are easier to visually process. While some visual details are lost, the gain in the ease of identifying streets and buildings may be a preferable outcome to a user more interested in navigating than in the shape of a roof or how many air conditioning units are on a given roof. In some embodiments, when the two-dimensional mapping information discussed above indicates a green space such as a park, the map tool may display a flat area without buildings. Further, in some cases, flat areas may be colored to indicate that the area is a green space, or a flat area may be colored blue to indicate that the area is a body of water.

In some embodiments, a map tool may receive input indicating a location in a map. For example, a user of multifunction device 300 or a user at a desktop computer may enter an address or otherwise indicate a certain location, such as Austin Children's Museum or the corner of Sixth Street and Congress Avenue.

Given a location in a map, the map tool may receive or request two-dimensional mapping information for the map. For example, the map tool may receive or request from Map Service 380 mapping information including footprints for objects within the area indicated through the location in the map.

Given the location in the map, the map tool may also receive or request height information for the map. For example, the map tool may receive or request from Map Service 380 mapping information that includes height values for various objects within the area indicated through the location in the map. The mapping information may be vector data instead of raster data.

The map tool may then, similar to the process described above in regard to FIG. 4A, correlate a location or point in the footprint of an object in the map region with a height value from the height information. In some cases, one or more points in or proximate to the footprint may be correlated to respective height values in the height information. For example, height values for each corner of the footprint, or a points along the perimeter, or only a single height value for somewhere near the center of the footprint. In some cases, given multiple points within the footprint, the map tool may select the highest height value from the respective, corresponding height values. In other cases, the map tool may calculate an average height value from the multiple height values corresponding to the respective points in the footprint. In other cases, the height and top of the extruded footprint may be created through the creation of a surface connecting each of different height values within a given footprint.

Similar to the creation of a three-dimensional model described above in regard to FIG. 4A, the map tool may render a three-dimensional representations of the objects based on the height information, where the rendering includes extruding a respective footprint for each object to create a respective three-dimensional version of the object through the addition of a height value, or height values, or a height value based on multiple height values. In some cases, the map tool may represent the collection of extruded footprints within a data structure storing the defining information for each of the extruded footprints, in addition to information for where within the map region the given extruded footprint exists.

Given a rendering of each extruded footprint, which is a three-dimensional object, the map tool may display a three-dimensional version of the three-dimensional object in a view of the map region. Upon displaying each of the generated three-dimensional objects, a user may see a version of the map region that is a simplified version of the map region, as compared to a raster-based map view or a photo-realistic version of the map region.

In some embodiments, the map tool may receive or request two-dimensional mapping information for a map or map region, where the two-dimensional mapping information includes a footprint for an object. The map tool may also receive or request three-dimensional mapping information for the map region, such as mesh data from Map Service 380, where the three-dimensional mapping information includes multiple height values corresponding to one or more locations in the map.

Given the two different kinds of mapping information, the map tool may correlate a given location of the footprint of the object with a respective height value from the multiple height values in the three-dimensional mapping information. In order for the correlation between the locations in the two-dimensional mapping information to height values in the three-dimensional mapping information to be valid, both sets of mapping information depict or describe an overlapping area of the map or map region.

Given a footprint for an object and at least one height value corresponding to the footprint, the map tool may extrude the footprint, based on the height value, to create a three-dimensional version of the object. The map tool may then display the three-dimensional version of the object. In the general case, the map tool may repeat the correlating and extruding processes for each footprint in the map region in order to display a complete three-dimensional view of the map region.

In some embodiments, the map tool may begin with the creation of a representation of map area, where the representation is divided into segments defined in terms of two-dimensional space. For example, the map area may correspond to a 200 square meter area, and each segment may be defined to correspond to a square meter. In other cases, segments may be defined in terms of other shapes.

The map tool may then request or receive three-dimensional mapping information for the map, where the three-dimensional mapping information includes height values corresponding to at least one point in each segment location. The map tool may then correlate a respective height value for each of the segments. In some cases, for a given segment, the map tool may correlate a height value from the center of the segment and for a point along each side of the segment.

Given the segments and respective height values, the map tool may generate a three-dimensional version of the segment through the addition of a respective height value to a respective segment. In this way, the map tool creates an extruded, three-dimensional version of the two-dimensional segment. This process may be repeated for each segment.

At this point, the map tool has generated a model with multiple segments of varying heights and may display a three-dimensional view of the map based on the model. If each of the segments is displayed as defined within the model, the result may be a mesh-like display of segments with lines bounding each segment. Therefore, in some cases, the map tool may smooth the segments, for example, if the height difference between adjacent segments is zero, small, or within a threshold value, then the map tool may merge the segments into one segment such that each adjacent side of the individual segments become a single surface. This process may be repeated for each segment in the model.

Given a map view based on the generated three-dimensional model, the map tool may receive input corresponding to a navigation operation or to a change in virtual camera viewpoint. For example, a user may wish to see, given a display of a building within a map view, the view from the other side of the building. In such a case, through a finger swipe, other gesture on a touch-sensitive screen, the map tool may update the map view in response to the user input. Further, given that the model information already exists within the model, the model does not need to be regenerated, meaning that no new mapping information is needed to provided the user with a new view of the map area.

In some embodiments, only footprints are subdivided into segments, and after the map tool performs the above-described smoothing/merging operation, the resulting three-dimensional version of the footprint may have a more accurate representation of the top of the building since each of the tops of each segments would have been smoothed together into one surface.

In some embodiments, a map view is updated as the user and multifunction device change positions or as a user on a desktop computer navigates within a map view. In such a case, the map view may be updated based on a combination of an already computed three-dimensional model augmented with computed model information for the new area displayed in the map as a result of the change in location. In this way, in this case, a complete recalculation of the 3D model is avoided, and only the area of the map that is new is used to augment the already generated 3D model.

In some cases, based on a projection of where the user is going, the map tool may prefetch corresponding mapping information, and if the projection is wrong or partially wrong, some or all of the prefetched mapping information may be discarded.

In some embodiments, the map tool may generate, based on multiple data sets, a three-dimensional model of a map region including multiple three-dimensional objects. The map tool may generate the three-dimensional model according to any of the above described method for generating a three-dimensional model.

The map tool may then display a map view based on the three-dimensional model. The map tool may, through an interface, input indicating a selection of an object in the three-dimensional model. In the case of a mobile device, the interface may be a touch-sensitive display screen. In the case of a desktop computer, the interface may a window and the input may be a selection of an object displayed in the window. In either case, based on the input, the map tool determines an object in the displayed three-dimensional model to select.

In some cases, given a map view, a user may adjust the virtual camera perspective from which the map is drawn. For example, given a constructed three-dimensional model as described, a user may view different sides of a building in the map view without using additional mapping information and based solely on the already constructed three-dimensional model.

Given a selected object, the map tool may invoke a function that extracts data from one or more of the data sets of mapping information from which the three-dimensional model was generated or from other data related to the map region. In some cases, the user may choose to display additional information regarding the selected object. For example, on a mobile device, a user may tap and hold a finger over a displayed object in the map view, the map tool may then provide the user with various options, such as adding a label, displaying an already assigned label for the object, displaying information regarding businesses within the building, whether or not the selected object is a point of interest, whether or not the object includes a restroom, among other options. In the case that the user adds a label, the user may choose for the label to be shared and the label information may be uploaded to Map Service 380 to be provided to other users. In some cases, the map tool may retrieve the additional information from Map Service 380.

In some cases, Map Service 380 may provide information collected from other users that have previously provided feedback or information regarding the selected object. This crowdsourced information may include such things as ratings for a restaurant within the building, comments on the cleanliness of a public restroom, or hours of operation of any businesses within the building.

In the case that the user selection may be satisfied based on the already received mapping information, the map view may be updated based on the specified function and data extracted from the mapping information data sets. For example, if the user selects to display a selected building with greater texture detail, the map tool may extract the information from the multiple data sets described above. However, in other cases, as described above, the map view may be updated based on information from other data sources.

Roof Analysis Tool Module

FIG. 8A illustrates an embodiment of an Roof Analysis Module 800. As noted above, the Roof Analysis Module 800 may implement each of the different embodiments of a roof analysis tool.

In some embodiments, Control Module 804 may receive Input 802, which may be various types of mapping data as described above with respect to FIGS. 4A-4E. Given mapping data, Control Module 804 may invoke Mapping Data Module 806 to process the mapping data and to identify, for a given footprint, multiple points on the roof of a structure corresponding to the footprint.

Based on the points in the roof, Normal Calculation Module 808 may calculate, in three-dimensional Cartesian coordinates, a respective normal for each respective point. Based on the calculated normals, Normal Clustering Module 810 may convert the three-dimensional Cartesian coordinates for each normal into spherical coordinates and apply a transformation in order to generate a two-dimensional output from which clusters of normals may be identified.

From the identified clusters of normals, Plane Identification Module 812 may determine a respective plane of a roof that corresponds to a respective cluster of normals from the identified cluster of normals.

From the identified planes of a roof, Archetypal Identification Module 814 may determine the classification of the roof type. Depending on the embodiment of the roof analysis tool, Parameterization Module 816 may generate a parameter set indicating a roof classification and an identification of a corresponding building for the roof, or Parameterization Module 816 may generate a parameter set describing coordinate data for each of the planes of a roof and an identification of a corresponding building for the roof.

The parameter set may then be provided as output 820 in order for the roof parameter set to be used as a basis for rendering a map view for a map region including the building for the roof.

Map Tool Module

FIG. 8B illustrates an embodiment of a Map Tool Module 850. As noted above, the Map Tool Module 850 may implement each of the different embodiments of a map tool.

In some embodiments, Control Module 854 may receive Input 852, which may be various types of mapping information, as described above with respect to FIGS. 4A-4E. Given the mapping information, Control Module 854 may invoke Model Generation Module 856 to generate a model of the surrounding environment, according to various embodiments discussed above.

Given a model of the surrounding environment, Control Module 854 may invoke User Interface Module 858 in response to various user inputs indicating, among other things, a selection of an object within a map view, information for labeling an object in the map view, or requesting more information or specific information regarding an object in the map view. In some cases, depending on the input, Map Tool Module 850 may communicate with Map Service 380 through Map Information Interface Module 860 to request or receive mapping information.

Depending on the embodiment and current state, Control Module 854 may provide a display of a map view as Output 870.

Example Computer System

FIG. 7 illustrates computer system 9900 that may execute the embodiments discussed above. In different embodiments, the computer system may be any of various types of devices, including, but not limited to, a personal computer system, desktop computer, laptop, notebook, or netbook computer, mainframe computer system, handheld computer, workstation, network computer, a camera, a set top box, a mobile device, a consumer device, video game console, handheld video game device, application server, storage device, a television, a video recording device, a peripheral device such as a switch, modem, router, or in general any type of computing or electronic device.

In one embodiment, computer system 9900 includes one or more processors 9360 a-9360 n coupled to system memory 9370 via input/output (I/O) interface 9380. The computer system further includes network interface 9390 coupled to I/O interface 9380, and one or more input/output devices 9382, such as cursor control device 9960, keyboard 9970, and one or more displays 9980. In some embodiments, it is contemplated that embodiments may be implemented using a single instance of a computer system, while in other embodiments may be implemented on multiple such systems, or multiple nodes making up a computer system, may be configured to host different portions or instances of embodiments. For example, in one embodiment some elements may be implemented via one or more nodes of the computer system that are distinct from those nodes implementing other elements.

In various embodiments, the computer system may be a uniprocessor system including one processor, or a multiprocessor system including several processors (e.g., two, four, eight, or another suitable number). The processors may be any suitable processor capable of executing instructions. For example, in various embodiments, the processors may be general-purpose or embedded processors implementing any of a variety of instruction set architectures (ISAs), such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. In multiprocessor systems, each of processors may commonly, but not necessarily, implement the same ISA.

In some embodiments, at least one processor may be a graphics processing unit. A graphics processing unit or GPU may be considered a dedicated graphics-rendering device for a personal computer, workstation, game console or other computing or electronic device. Modern GPUs may be very efficient at manipulating and displaying computer graphics, and their highly parallel structure may make them more effective than typical CPUs for a range of complex graphical algorithms. For example, a graphics processor may implement a number of graphics primitive operations in a way that makes executing them much faster than drawing directly to the screen with a host central processing unit (CPU). In various embodiments, the content object processing methods disclosed herein may, at least in part, be implemented with program instructions configured for execution on one of, or parallel execution on two or more of, such GPUs. The GPU(s) may implement one or more application programmer interfaces (APIs) that permit programmers to invoke the functionality of the GPU(s). Suitable GPUs may be commercially available from vendors such as NVIDIA Corporation, ATI Technologies (AMD), and others.

System memory within the computer system may be configured to store program instructions and/or data accessible from a processor. In various embodiments, the system memory may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type of memory. In the illustrated embodiment, program instructions and data may implement desired functions, such as those described above for the various embodiments are shown stored within system memory 9370 as program instructions 9925 and data storage 9935, respectively. In other embodiments, program instructions and/or data may be received, sent or stored upon different types of computer-accessible media or on similar media separate from system memory or the computer system. Generally, a computer-accessible medium may include storage media or memory media such as magnetic or optical media, e.g., disk or CD/DVD-ROM coupled to the computer system via the I/O interface. Program instructions and data stored via a computer-accessible medium may be transmitted from transmission media or signals such as electrical, electromagnetic, or digital signals, which may be conveyed via a communication medium such as a network and/or a wireless link, such as may be implemented via the network interface.

In one embodiment, the I/O interface may be configured to coordinate I/O traffic between the processor, the system memory, and any peripheral devices in the device, including a network interface or other peripheral interfaces, such as input/output devices. In some embodiments, the I/O interface may perform any necessary protocol, timing or other data transformations to convert data signals from one component into a format suitable for another component to use. In some embodiments, the I/O interface may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of the I/O interface may be split into two or more separate components, such as a north bridge and a south bridge, for example. In addition, in some embodiments some or all of the functionality of the I/O interface, such as an interface to system memory, may be incorporated directly into the processor.

The network interface of the computer system may be configured to allow data to be exchanged between the computer system and other devices attached to a network, such as other computer systems, or between nodes of the computer system. In various embodiments, the network interface may support communication via wired or wireless general data networks, such as any suitable type of Ethernet network, for example; via telecommunications/telephony networks such as analog voice networks or digital fiber communications networks; via storage area networks such as Fibre Channel SANs, or via any other suitable type of network and/or protocol.

The I/O devices may, in some embodiments, include one or more display terminals, keyboards, keypads, touchpads, scanning devices, voice or optical recognition devices, or any other devices suitable for entering or retrieving data from one or more computer systems. Multiple I/O devices may be present in the computer system or may be distributed on various nodes of the computer system. In some embodiments, similar I/O devices may be separate from the computer system and may interact with one or more nodes of the computer system through a wired or wireless connection, such as over the network interface.

The memory within the computer system may include program instructions configured to implement each of the embodiments described herein. In one embodiment, the program instructions may include software elements of embodiments of the modules discussed earlier. The data storage within the computer system may include data that may be used in other embodiments. In these other embodiments, other or different software elements and data may be included.

Those skilled in the art will appreciate that the computer system is merely illustrative and is not intended to limit the scope of the embodiments described herein. In particular, the computer system and devices may include any combination of hardware or software that can perform the indicated functions, including a computer, personal computer system, desktop computer, laptop, notebook, or netbook computer, mainframe computer system, handheld computer, workstation, network computer, a camera, a set top box, a mobile device, network device, internet appliance, PDA, wireless phones, pagers, a consumer device, video game console, handheld video game device, application server, storage device, a peripheral device such as a switch, modem, router, or in general any type of computing or electronic device. The computer system may also be connected to other devices that are not illustrated, or instead may operate as a stand-alone system. In addition, the functionality depicted within the illustrated components may in some embodiments be combined in fewer components or distributed in additional components. Similarly, in some embodiments, the functionality of some of the illustrated components may not be provided and/or other additional functionality may be available.

Those skilled in the art will also appreciate that, while various items are illustrated as being stored in memory or on storage while being used, these items or portions of them may be transferred between memory and other storage devices for purposes of memory management and data integrity. Alternatively, in other embodiments some or all of the software components may execute in memory on another device and communicate with the illustrated computer system via inter-computer communication. Some or all of the system components or data structures may also be stored (e.g., as instructions or structured data) on a computer-accessible medium or a portable article to be read from an appropriate drive, various examples of which are described above. In some embodiments, instructions stored on a computer-accessible medium separate from the computer system may be transmitted via transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as a network and/or a wireless link. Various embodiments may further include receiving, sending or storing instructions and/or data implemented in accordance with the foregoing description upon a computer-accessible medium. Accordingly, the present invention may be practiced with other computer system configurations.

CONCLUSION

Various embodiments may further include receiving, sending or storing instructions and/or data implemented in accordance with the foregoing description upon a computer-accessible medium. Generally, a computer-accessible medium may include storage media or memory media such as magnetic or optical media such as disks or DVD/CD-ROM, volatile or non-volatile media such as RAM, ROM, flash drives, as well as transmission media or signals such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as network and/or a wireless link.

The various methods described herein represent example embodiments of methods. These methods may be implemented in software, hardware, or through a combination of hardware and software. The order of the method steps may be changed, and various elements may be added, reordered, combined, omitted, or modified.

Various modifications and changes may be made as would be obvious to a person skilled in the art having the benefit of this disclosure. It is intended that the invention embrace all such modifications and changes and, accordingly, the above description to be regarded in an illustrative rather than a restrictive sense. 

What is claimed is:
 1. A method, comprising: performing, by one or more computing devices: accessing footprint data for one or more structures within a map region; identifying, from a three-dimensional data set corresponding to the map region and based on the footprint data for a structure of the one or more structures within the map region, a plurality of points on a roof of the structure; calculating, based on the plurality of points on the roof of the structure, a plurality of groups of normals; identifying, for each respective group of normals within the plurality of groups of normals, a respective plane of the roof; and determining a parameter set for the roof of the structure based on parameter values describing each respective plane of the roof.
 2. The method of claim 1, wherein said determining further comprises identifying, based on each respective plane of the roof, a classification of a roof type.
 3. The method of claim 2, wherein said determining further comprises basing the parameter set on an identification value for the classification of the roof type and an identification of the structure for which the roof corresponds.
 4. The method of claim 1, wherein said calculating the plurality of groups of normals comprises: generating a two-dimensional histogram based on a Hough transformation of spherical coordinates for each of a plurality of normals.
 5. The method of claim 4, further comprising determining a classification of a roof type based on the respective orientation of each respective plane of the roof.
 6. A system, comprising: a computing device comprising at least one processor; and a memory comprising program instructions, wherein the program instructions are executable by the at least one processor to: access footprint data for one or more structures within a map region; identify, from a three-dimensional data set corresponding to the map region and based on the footprint data for a structure of the one or more structures within the map region, a plurality of points on a roof of the structure; calculate, based on the plurality of points on the roof of the structure, a plurality of groups of normals; and identify, based on the plurality of groups of normals, a roof type classification for the structure.
 7. The system of claim 6, wherein to identify the roof type classification for the structure, the program instructions are further executable by the at least one processor to determine, for each respective group of normals within the plurality of groups of normals, a respective plane of the roof.
 8. The system of claim 7, wherein to identify the roof type classification for the structure, the program instructions are further executable by the at least one processor to determine, for each respective plane of the roof, a respective orientation based on an average normal for a respective group of normals of the plurality of normals.
 9. The system of claim 8, wherein to identify the roof type classification for the structure, the program instructions are further executable by the at least one processor to determine, based on a respective orientation for each respective plane of the roof, a similarity between the respective orientation for the respective plane of the roof and an orientation of a plane of an archetypal roof for the roof type classification.
 10. The system of claim 9, wherein the roof type classification is determined to be similar when less than all planes of the archetypal roof are determined to be similar to the respective planes of the roof of the structure.
 11. A computer-readable storage medium storing program instructions, wherein the program instructions are computer-executable to implement: receiving, for a map region, three-dimensional mapping data comprising a plurality of triangles representing a respective plurality of surface regions for objects in the map region; identifying a subset of triangles of the plurality of triangles, wherein the subset of triangles correspond to a roof for a building in the map region; calculating a normal for a surface of a triangle within the subset of triangles, wherein the normal is represented in three-dimensional Cartesian coordinates; transforming the three-dimensional Cartesian coordinates of the normal for the surface of the triangle into spherical coordinates for a unit sphere; and eliminating high variance in a range of azimuth angles in the theta-phi spherical coordinates due to a range of z-axis values in the three-dimensional Cartesian coordinates for the normal for the surface of the triangle, wherein said eliminating comprises: transforming the three-dimensional Cartesian coordinates of the normal for the surface of the triangle into rho angle and psi angle parameters instead of theta angle and phi angle parameters.
 12. The computer-readable storage medium of claim 11, wherein the range of azimuth angles is 360 degrees due to z-axis values for normals for the surfaces of the subset of triangles.
 13. The computer-readable storage medium of claim 12, wherein the program instructions are computer-executable to further implement: determining, for each plane in the roof and based on the rho angle and psi angle parameters, a respective plane orientation.
 14. The computer-readable storage medium of claim 11, wherein the program instructions are computer-executable to further implement generating a two-dimensional histogram based on a Hough transformation of spherical coordinates for each of a plurality of normals for the subset of triangles.
 15. The computer-readable storage medium of claim 14, wherein the program instructions are computer-executable to further implement identifying a plane of a roof for a building based on the two-dimensional histogram.
 16. A method, comprising: performing, by one or more computing devices: identifying, from a three-dimensional data set corresponding to a map region, a plurality of points on a roof of a structure within the map region. calculating, based on the plurality of points on the roof of the structure, a plurality of normals perpendicular to the roof of the structure; clustering the plurality of normals into a plurality of groups of normals; identifying, for each respective group of normals within the plurality of groups of normals, a respective plane of the roof of the structure; and identifying, based on each respective plane of the roof, a classification for a roof type.
 17. The method of claim 16, wherein said identifying the classification for the roof type further comprises determining that one or more planes of a stored archetype for a roof type are oriented similarly to a corresponding one or more planes of the planes of the roof.
 18. The method of claim 16, wherein said identifying the plurality of points on the roof of the structure within the map region further comprises using a subset of the three-dimensional data set corresponding to an area of the map region defined by a footprint of the structure.
 19. The method of claim 16, wherein said clustering further comprises generating a two-dimensional histogram based on spherical coordinates for each of a plurality of normals.
 20. The method of claim 16, further comprising determining a respective shape for each respective plane of the roof based on a tangent plane.
 21. A method, comprising: performing, by a mobile computing device: generating a three-dimensional model based on mapping data for a map region, wherein the three-dimensional model comprises representations for buildings in the map region; receiving, from a server, roof type classifications corresponding to the buildings in the map region; and rendering, based on the three-dimensional model and based on the roof type classifications for the buildings in the map region, a map view of the map region such that each respective building in the map view has a rendered roof based on a respective roof type classification of the roof type classifications.
 22. The method of claim 21, wherein said generating the three-dimensional model comprises: receiving two-dimensional mapping information for the map region, wherein the two-dimensional mapping information includes a respective footprint for the buildings in the map region; receiving height information for the one or more buildings in the map region, wherein the height information includes a respective height value corresponding to each respective building of the buildings in the map region; and generating three-dimensional representations of the one or more buildings based on the height information, wherein said generating the three-dimensional representations comprises extruding a respective footprint of each given building of the one or more buildings to create a respective three-dimensional version of the given building.
 23. The method of claim 21, wherein prior to said rendering: determining that a shape of a building in the map region does not match a roof shape corresponding to a roof type classification for the building; and determining a rendering for the building based on adjusting the roof shape corresponding to the roof type classification to fit the shape of the building.
 24. The method of claim 21, wherein the mapping information is vector data and not raster data.
 25. The method of claim 21, wherein one or more roof type classifications of the roof type classifications are randomly selected based on zoning information corresponding to the map region. 